Closed nkakouros closed 5 years ago
Hmmmm can you make that fix a configurable option? I'm using a lot of buffers in my window open to compare colors and Colorizer makes it very easy to compare them visually. That's not possible anymore with this fix :-/
Yeah, I wondered why initially the BufLeave
autocommand was commented out (because I don't remember the reason). How are you using the plugin, so that it is broken for you now?
Yeah, I wondered why initially the
BufLeave
autocommand was commented out (because I don't remember the reason). How are you using the plugin, so that it is broken for you now?
I'm using it a lot to manage my colorschemes (vim via lifepillar/vim-colortemplate, termite, awesomewm) and to have the same colours everywhere. So I have two or more buffers open with the colorschemes and it's easier to compare the colours in a glance with Colorizer than checking the hex-codex ...
With the latest fix the colorization is gone as soon as I switch buffers :-/
Okay, I made this configurable commit 8dcb8daa0b446f8115a4bda51ea72f5b4b26e1a4
If you don't want the default behaviour, use :let g:colorizer_disable_bufleave=1
Thank you so much! This is perfect :-D
Here are two demo files:
and
Save them, close nvim and open them the first file. Part of line 12 will be red correctly. Now, open the second file (eg
nvim b.sh
). Line 12 is also red (hopefully your colorscheme does not print variables red).I use neovim.