-
-
Notifications
You must be signed in to change notification settings - Fork 246
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
Bad highlighting in .gitignore files using tree-sitter #734
Comments
After searching among this and other colorschemes, I'm sure that this appearance is caused by:
And it's common to link the special character like this. Could you please provide a "expected behavior" image, so that we can decide what/how to change, as changing any of them may break some other user interface. |
It can, but changing that might also affect the UI in some other places. This should be with further consideration I guess |
According to neovim documentation this is the intended way:
|
Ah, I just found that I misread your advice here 😉
This seems to be a acceptable solution, though I'm not sure if this should be implemented on upstream (nvim-treesitter) or we write custom |
I don't think this is an upstream issue, nvim-treesitter only provides the queries, its the colorscheme responsibility to give them a useful color. I don't think queries are necessary either, just doing something like |
Description
A recent commit in nvim-treesitter change the highlighting for wildcards and characters in .gitignore. The new captures link to the same
Special
group in catppuccin, which makes wildcards hard to distinguish:Neovim version
Terminal and multiplexer
kitty 0.35.2
Catppuccin version / branch / rev
main
Steps to reproduce
nvim -u repro.lua
Example .gitignore:
Expected behavior
Wildcards should stand out from the file/directory names.
Actual behavior
Almost everything is the same color and makes it hard to read.
Repro
The text was updated successfully, but these errors were encountered: