nvim-lsp-smag
lsp-trouble.nvim
nvim-lsp-smag | lsp-trouble.nvim | |
---|---|---|
3 | 4 | |
77 | 384 | |
- | - | |
0.0 | 6.7 | |
over 1 year 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.
nvim-lsp-smag
-
Q: Refresh vsplit if exists rather than opening new vsplit?
What I do is to use lsp-smag and the default keybindings to open tags in the preview window.
-
Floating Tag Preview - also for LSP
A minimal plugin to preview tags in a floating window. If you use nvim-lsp-smag this just works for LSP location as well. In the above GIF you can see previewing the implementation and declaration of the object under the cursor. A tiny plugin that just extends the native preview commands. Though it remains highly customizable.
- Make the LSP integration even more simple - use language server locations as tags
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?
trouble.nvim - 🚦 A pretty diagnostics, references, telescope results, quickfix and location list to help you solve all the trouble your code is causing.
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
toggle-lsp-diagnostics.nvim - Neovim plugin for toggling the LSP diagnostics.
nvim-floating-tag-preview - Preview tags in a floating window
lspsaga.nvim - improve neovim lsp experience [Moved to: https://github.com/nvimdev/lspsaga.nvim]
bufferline.nvim - A snazzy bufferline for Neovim
nvim-lspfuzzy - A Neovim plugin to make the LSP client use FZF
lspsaga.nvim - improve neovim lsp experience
babelfish.nvim - The answer to the ultimate question is :help 42
doom-nvim - A Neovim configuration for the advanced martian hacker [Moved to: https://github.com/doom-neovim/doom-nvim]