feat(highlights): colored underlined LSP diagnostics #36
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is amazing, I was not aware that it's possible. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default, Neovim uses a color to underline LSP diagnostics. The color matches the severity of the diagnostic, and is very useful to be able to quickly identify multiple diagnostic severities appearing on the same line:
The colorscheme currently doesn't color underlined LSP diagnostics. The example below isn't particularly realistic, but I encountered the case multiple times in Go and Rust codebases, and had to jump to each diagnostic individually (or call
vim.diagnostic.open_float()) to be able to identify their severity:After the changes from this PR, colored underlines are restored: