toggle-lsp-diagnostics.nvim
lsp-trouble.nvim
toggle-lsp-diagnostics.nvim | lsp-trouble.nvim | |
---|---|---|
5 | 4 | |
94 | 384 | |
- | - | |
3.9 | 6.7 | |
9 days ago | almost 3 years ago | |
Lua | Lua | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
toggle-lsp-diagnostics.nvim
- How do you turn off the yellow highlighting after your done with the search?
-
How can I hide the hint diagnostic messages (shown in white text) for only Python? Using nvim-cmp and Pyright.
For files I didn't write and trigger many errors I toggle just all diagnostics, I use a plugin for that https://github.com/WhoIsSethDaniel/toggle-lsp-diagnostics.nvim
-
How disable and reenable builtin LSP (client)
Are enable/disable fairly new (also show())? I don't remember them when I was writing [toggle-lsp-diagnostics](https://github.com/WhoIsSethDaniel/toggle-lsp-diagnostics.nvim). I recall having to use display() (which was and remains undocumented AFAIK). I know about the vim.diagnostic / vim.lsp.diagnostic name switch, but I don't recall these functions being available in 0.5.0. I suppose what I'm asking is "do I need to use display() if I want to support 0.5.0?"
-
How to toggle inline LSP warnings/errors
You can try https://github.com/WhoIsSethDaniel/toggle-lsp-diagnostics.nvim.
lsp-trouble.nvim
-
Trouble: Just pushed a big update with support for lsp references, location lists and quickfix lists
Just added Telescope actions support. Works with any search results in Telescope. Pretty cool :)
-
How to change icons and colors, to make my LSP diagnostics look better?
Yeah, I might consider to switch back to CoC later. I was able to make a configuration which I'm comfortable with, it resembles CoC's behavior a bit, but I've found some sort of slowness in the startup process, like it sometimes takes a few seconds to load, sometimes a few diagnostics don't show. So far I have only tested it with rust-analyzer, let's see how everything goes. Anyways, I'm just giving the native LSP a try and also because of the hype I had with some plugins like lsp-trouble.nvim lol. And of course to make my neovim config to feel more lightweight. But maybe I should just wait that the LSP is mature enough.
-
LSP Trouble: A pretty diagnostics list to help your solve all the trouble your code is causing.
I created a little plugin that shows a pretty list of LSP diagnostics.
What are some alternatives?
nvim-lspconfig - Quickstart configs for Nvim LSP
trouble.nvim - 🚦 A pretty diagnostics, references, telescope results, quickfix and location list to help you solve all the trouble your code is causing.
nvim-highlite - A colorscheme generator that is "lite" on logic for the developer.
lspsaga.nvim - improve neovim lsp experience [Moved to: https://github.com/nvimdev/lspsaga.nvim]
nvim-dap - Debug Adapter Protocol client implementation for Neovim
nvim-lsp-smag - Seamless integration of language server locations into NeoVim
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
bufferline.nvim - A snazzy bufferline for Neovim
neovim - Vim-fork focused on extensibility and usability
nvim-lspfuzzy - A Neovim plugin to make the LSP client use FZF
lspsaga.nvim - improve neovim lsp experience