Closed gbrlsnchs closed 3 years ago
And now the PR is merged; the new LSP diagnostic highlight names are listed here: https://github.com/neovim/neovim/blob/35325ddac04b1b59b7982797021cdaabdabc87fb/runtime/doc/lsp.txt#L376
Done. Seems visually nice to me.
The doc mentions that "Sign, underline and virtual text highlights (by default) are linked to their
corresponding LspDiagnosticsDefault highlight . Since you're not changing anything for LspDiagnosticsVirtualText*
LspDiagnosticsFloating*
LspDiagnosticsSign*
maybe these lines can be removed?
This is what onedark.vim does (disclaimer: PR was from me).
Done, @ojroques! Thanks for the tip.
Glad to help. I would have kept these lines though since they differ from the defaults:
call s:hi("LspDiagnosticsUnderlineWarning" , s:nord13_gui, "", s:nord13_term, "", "undercurl", "")
call s:hi("LspDiagnosticsUnderlineError" , s:nord11_gui, "", s:nord11_term, "", "undercurl", "")
call s:hi("LspDiagnosticsUnderlineInformation" , s:nord8_gui, "", s:nord8_term, "", "undercurl", "")
call s:hi("LspDiagnosticsUnderlineHint" , s:nord10_gui, "", s:nord10_term, "", "undercurl", "")
The underline text is quite useful to spot warnings/errors.
You're totally right, my bad. Just included those again.
With LspDiagnosticsUnderline*
stuffs specified, it would be buggy of showing colors. However, using LspDiagnosticsDefault*
looks okay. 👌
With
LspDiagnosticsUnderline*
stuffs specified, it would be buggy of showing colors. However, usingLspDiagnosticsDefault*
looks okay.
How come? I'm using my fork with this PR applied and everything seems fine.
With
LspDiagnosticsUnderline*
stuffs specified, it would be buggy of showing colors. However, usingLspDiagnosticsDefault*
looks okay.How come? I'm using my fork with this PR applied and everything seems fine.
okay, works perfectly on another machine. this is weird.
With
LspDiagnosticsUnderline*
stuffs specified, it would be buggy of showing colors. However, usingLspDiagnosticsDefault*
looks okay.How come? I'm using my fork with this PR applied and everything seems fine.
okay, works perfectly on another machine. this is weird.
Might be your Neovim version maybe? Anyway, good it's working!
Just a heads-up: these will change again (for the last time?) once https://github.com/neovim/neovim/pull/12655 is merged.