Closed dedguy21 closed 1 year ago
Please review, again just adding lsp group to the color scheme so the new lsp semantic highlights don't discolor the settings.
more testing needed, will reopen later.
It ready for review, a couple of links in LSP group don't link back to a Treesitter group because you don't seem to use them in the color scheme. But it isn't causing issues that i have tested
Hey @dedguy21 thanks for the PR. I've been testing your changes with several languages to look for any possible problem and I found that, mentioning a case, some elements' highlights from Rust like traits, unions and enums now lack of a proper syntax highlight.
Please consider testing in an exhaustive manner the changes you made and then send to us the corrections. Thank you!
Edit:
@MrFixThis
Apologies, I'm only a data analyst. So I can test python and some scripting languages and such. But rust, c, c++, etc are beyond my knowledge.
Does there exist a code snippet bank for syntax highlight testing these different languages?
@MrFixThis I'm wondering if you cleared your nvim cache from ~/.local and ~/.cache (on Linux), because I'm not having any highlighting issues you pointed out.
more extensive testing needed
Fix an issue with color where semantic highlighting in nvim 0.9 new lsp group was causing an issue. Also I thought it would be useful to include lazy.nvim plugin manager as well. It is quickly become the new defacto for nvim.