-
Notifications
You must be signed in to change notification settings - Fork 15
[IMPORTANT] Deprecation & Transition Strategy #73
Comments
nvim-lua/diagnostic.nvim is deprecated. [migration guide](nvim-lua/diagnostic-nvim#73)
nvim-lua/diagnostic.nvim is deprecated. [migration guide](nvim-lua/diagnostic-nvim#73)
nvim-diagnostics plugin is now deprecated: nvim-lua/diagnostic-nvim#73
Can someone please show me to how to do this |
have you tried |
Oh, hey that worked. Thanks! |
Was someone able to change the signs icons? I tried several ways but nothing worked. |
have you tried
|
Yep, I tried this in the init.vim and all the possible lua versions vim.api.nvim_call_function("sign_define", {"LspDiagnosticsErrorSign", I tried them on_attach, in the new beforeDiagnostick callback, before and after any lsp setting, noone worked, to me. |
That todo is for a different thing (there was some error when trying to find the signs that had been displayed. it's an internal bug I think, not related or due to the code). Have you tried it via the ex command, not using |
No worries, cosmetics is not as important as functionalities, and for now LSP is a great piece of software so I can definitely wait. (truth is I don't know know what parameters to pass to :lua vim.lsp.diagnostic.set_signs, still a newb on lua :D) |
Ah, I meant to just try the ex commands listed in the docs to configure the signs. |
Wow, I am truly sorry. LspDiagnosticsErrorSign => LspDiagnosticsSignError I'm gonna hide behind a mountain. |
😆 such is life. No worries. I changed the names in the PR because they were randomly named before and now follow a pattern, so at least you're not too crazy :) |
Might wanna archive this repo, maybe. |
autocmd CursorHold * lua vim.lsp.diagnostic.show_line_diagnostics{focusable=false}
|
Now that neovim/neovim#12655 is merged, we are deprecating diagnostic-nvim. For full information and commit message, see: neovim/neovim@f75be5e
Any features that were in diagnostic-nvim have now been implemented in Neovim core! This was always the plan for diagnostic-nvim, as it was a playground and testing area for features and interfaces for the builtin LSP
You should remove any
on_attach
calls fromdiagnostic-nvim
in your configuration. They are no longer required.Common Actions
PrevDiagnosticCycle
andNextDiagnosticCycle
:vim.lsp.diagnostic.goto_prev()
vim.lsp.diagnostic.goto_next()
nnoremap <leader>dn <cmd>lua vim.lsp.diagnostic.goto_next()<CR>
PrevDiagnostic
andNextDiagnostic
vim.lsp.diagnostic.goto_prev { wrap = false }
vim.lsp.diagnostic.goto_next { wrap = false }
nnoremap <leader>dn <cmd>lua vim.lsp.diagnostic.goto_next { wrap = false }<CR>
OpenDiagnostic
vim.lsp.diagnostic.set_loclist()
Configuring LSP Diagnostic Display
lsp-handler
s.:help lsp-handler
Also note, the highlight group names have changed to now be consistent with each other. From the commit message in neovim core:
For example, the highlight that was formerly
LspDiagnosticsError
is nowLspDiagnosticsVirtualTextError
. It can also be configured by changing the default highlight group,LspDiagnosticsDefaultError
. For more information, read:help lsp-highlight-diagnostics
.Advanced configuration
The text was updated successfully, but these errors were encountered: