-
-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BufferLine wrong buffer highlighting #218
Labels
assigned
Under progress.
Comments
I also meet the problem, and my system is archlinux, neovim version is nightly, and the neovim client neovide |
Same here! macOS + iTerm2 |
ellisonleao
added a commit
to ellisonleao/neovimfiles
that referenced
this issue
Jan 16, 2023
- add override for bufferline bug. Ref projekt0n/github-nvim-theme#218
This issue still persists |
During the refactoring process, I resolved the issue but forgot to reference it. To ensure the fix is implemented, please use commit 4d5a4ce on the main branch or a later revision. |
Closing due to inactivity. Can reopen later. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
Recently I updated my neovim plugins after not doing it for about 3 months and to my surprise this broke the unselected buffers highlighting in bufferline.nvim without me changing anything.
Before:
After:
I looked at the commit history since my last update and this one c306cbd grabbed my attention.
When I remove the line
BufferLineBackground = { fg = c.syntax.comment }
I always get the initial behaviour regardless if I am only usingBufferLineIndicatorSelected = { fg = c.syntax.param }
or the originalBufferLineIndicatorSelected = { fg = c.blue }
Am I misunderstanding something or was there a mistake with this commit?
My configuration does not have any custom highlighting for bufferline.nvim it always worked out of the box with this colorscheme.
I am using Neovim 0.8.1 with iTerm on macOS.
My terminal's colorscheme is the one from projekt0n/github-theme-contrib.
The text was updated successfully, but these errors were encountered: