Open aketchum15 opened 1 month ago
If I had to guess, I would say you're right in thinking WSL has something to do with it 🤔
Can you reproduce this on Neovim in Windows (e.g. w/ Neovide)?
I set up a minimal install of nvim in windows (lazy.nvim, and barbar) and it works fine over there... I also tested on my native linux machine last night and that works as well
Not sure what's going on, we really need reproduction steps (environment, config, etc) to be able to debug this.
I went ahead and tried a minimal config to reproduce the issue but it actually doesn't happen with just lazy and barbar (even with options in setup). I probably should've done this earlier, my bad. Any ideas on how I could narrow down what's interacting with barbar to cause this issue?
Good ol' binary search: disable half your plugins, test, narrow it down, until you get the one that triggers the issue.
Description
whenever using :BufferNext, :BufferPrevious, or BufferClose the highlighting in the bar does not update to reflect the current buffer, nor does the list change. Additionally, making changes to any buffer but the first in the list does not result in the bar updating to show that the buffer is changed, and adding a buffer to the session whether through telescope or just :badd does not cause the bar to update with the new buffer. Interestingly, moving buffers or sorting buffers does result in the correct animation/order. I can get the bar to update manually by using :BarBarEnable.
To Reproduce
default config with the plugin. I do have keymaps for :BufferNext/:BufferPrevious, but the issue occurs whether I use the command or keymap.
Steps to reproduce the behavior: open multiple buffers :BufferNext/:BufferPrevious/:BufferDelete/:badd
Information Neovim version: v0.10.0 installed from releases page of nvim github I am using wsl which may have something to do with it