search

akinsho / bufferline.nvim

A snazzy bufferline for Neovim
GNU General Public License v3.0
3.51k stars 198 forks source link

[Bug]: Bright foreground color being applied to active tab instead of filename #597

Closed gallor closed 2 years ago

gallor commented 2 years ago

Is there an existing issue for this?

What happened?

The issue is that the foreground color to the active tab is a bright highlight. I can directly modify it via the highlight groups but I have been unable to get it just "work" out of the box. I have tried under multiple colorschemes (monokai, hybrid, firewatch, evening) and even with a fully stripped vimrc that only included loading the plugin and dev-icons, setting the termguicolors and registering the 2 plugins. I'm using a patched font (InconsolataGo) and have tried on both Mac on iTerm2 (the nerd font is selected) and on Ubuntu terminal (also with nerd font Inconsolata). Am I missing some kind of configuration? Thanks! SCR-20221027-nj7

What did you expect to happen?

Expected behaviour: To not have the bright background and instead have the text turn that color.

Config

" This is a barebones vimrc that I used to still recreate the issue in iTerm2 on OSX set termguicolors call plug#begin('~/.local/share/nvim/plugged') Plug 'kyazdani42/nvim-web-devicons' " File icons for explorer Plug 'akinsho/bufferline.nvim', { 'tag': 'v3.*' } Plug 'rakr/vim-two-firewatch' " colorscheme for example call plug#end() colorscheme two-firewatch :lua require('nvim-web-devicons').setup{} :lua require('bufferline').setup{}

Additional Information

...

commit

No response

akinsho commented 2 years ago

@gallor this seems very likely to be a configuration rather than a plugin issue. Are you using tmux? That can often cause highlighting issues.

gallor commented 2 years ago

🤦 I hadn't even thought about tmux. Good call. Yes, I ssh into a remote box running tmux to run everything. I'm looking into some solutions on how to resolve this as it appears to be related with tmux and rendering italics. Feel free to close and I can update this later if I find a solution that might benefit someone else (or would a PR to update the docs be better?) Thanks!

akinsho commented 2 years ago

@gallor I don't think specific tmux fixes should go in the README since not everyone uses that myself included. You could add any info to the wiki but tbh I find tmux stuff changes and this information is already spread out in blogs