Closed FernandoBasso closed 2 years ago
I think the problem is something else. It is working.
I open the typescript file, and TheType
is not dimmed. If I run :edit
or use then unuse the type, and it gets dimmed out.
PS: This is not a real problem for me, and it is not true that it doesn't dim unused types. I'm OK with closing this issue.
What a color scheme does is to define highlight groups, it doesn't actually highlight the text. Instead, it's done via highlight engines like built-in vim syntax engine and coc, they read the color code in predefined hi groups and highlight the text.
So if it sometimes dim, it means the highlight engine could those hi groups.
IMO this bug is caused by coc or coc-tsserver.
Operating system/version
Arch Linux (rolling release)
Terminal emulator/version
Terminator 2.1.1 from the repositories
$TERM environment variable
xterm-256color
Tmux version
No response
Feature matrix
Minimal vimrc that can reproduce this bug.
NOTE: I get the same result whether or not I uncomment the tree-sitter lua section.
Steps to reproduce this bug using minimal vimrc
Here's a screenshot in Vim, with original Gruvbox:
Note how
TheType
is dimmed/grayed out. And here's a screenshot with Neovim 6.1, with TreeSitter and gruvbox-material:In both cases I'm using coc.vim with a TypeScript buffer.
I tried to look at the source code for gruvbox-material but couldn't find out if this feature is just not-implemented, or I am lacking some configuration. I see
highlight! link CocFadeOut Grey
in thegruvbox-material.vim
file but not sure why it is not kicking in.This is my current gruvbox-material configuration:
This might be relevant: https://github.com/neoclide/coc.nvim/issues/1046.
Expected behavior
The expected behavior is that the unused
TheType
is grayed out or dimmed out just asfnF
orunusedParam
.Actual behavior
We don't get dimmed out/grayed out syntax for unused types (other stuff are dimmed or not dimmed correctly).