Not working on Neovim

[Eustáquio Rangel]

I just got an error when running this plugin on Neovim. Seems that there is an error on the hex2rgb function, because is not send an hex value there. I forced synIDattr to use the gui mode (last parameter) and the error stopped, but I still can't have the dimmed parts of the code.

[Eustáquio Rangel]

Hello? :-)

[Junegunn Choi]

The error only occurs when termguicolors is set. But it works fine on regular Vim with the option.

colo seoul256
echo synIDattr(synIDtrans(hlID('Normal')), 'fg#')
" vim: 252, nvim: 252
set termguicolors
echo synIDattr(synIDtrans(hlID('Normal')), 'fg#')
" vim: #d9d9d9, nvim: 252

@justinmk Any idea why I see different results?

[Eustáquio Rangel]

Maybe is Neovim returning it wrong?

[Eustáquio Rangel]

Does regular Vim has the set termguicolors?

[Junegunn Choi]

Yes.
vim/vim@61be73b

[Justin M. Keyes]

@junegunn @taq What version of Neovim ? There was a patch related to this not long ago.

neovim/neovim#4851

[Eustáquio Rangel]

I use the latest version from the Neovim PPA. They update it almost every day.

[Justin M. Keyes]

When are you calling set termguicolors?

nvim --cmd 'set termguicolors' -c "put =synIDattr(synIDtrans(hlID('Normal')), 'fg#')"

Inserts #f8f8f2 for me. set termguicolors must be called during startup (in your vimrc/init.vim), not after. This is a nvim limitation (documented at :help 'termguicolors').

[Eustáquio Rangel]

I think is on some script or even a color scheme. I'm away from the computer (thanks God I can have some hours off sometimes) but I'll test put it on startup tomorrow and give and answer here.

[Eustáquio Rangel]

Hey, using set termguicolors on startup worked, thanks!