trouble.nvim
lspsaga.nvim
Our great sponsors
trouble.nvim | lspsaga.nvim | |
---|---|---|
59 | 10 | |
4,722 | 3,246 | |
- | 1.9% | |
7.6 | 9.3 | |
7 days ago | 2 days ago | |
Lua | Lua | |
Apache License 2.0 | 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.
trouble.nvim
-
How to copy LSP diagnostics from folke/trouble to quickfix window?
Does anyone know if it's possible to copy the LSP diagnostics (which currently is being displayed using folke/trouble to the quickfix window?
-
Help with trouble.nvim
A newbie here, I used jose-elias-alvarez/null-ls.nivm for diagnostics and formatting, but I recently discovered folke/trouble.nvim and for me, it seems like a better option However, I don't know if it supports formatting and linting, I don't even know if it is an alternative to null-ls. So I need your help, can trouble.nvim replace null-ls? If not, can I use both of them simultaneously?
-
How can i get better looking errors?
Trouble
-
How do I get neovim to only show LSP errors as underline squiggles and not in the gutter?
Looking at the screenshot here for example https://github.com/folke/trouble.nvim they show errors both in the gutter and underlined.
-
Neovim vs VSCode Neovim - what are the tradeoffs?
All you need is just the LSP working (with linter, formatter and diagnostics) and telescope. Seriously, telescope is the GOAT, way faster than a file tree, you end up using the filetree only to move, create and delete files/folders but if it's just for that, you might as well use the terminal instead. For the LSP, it's not only autocompletion and hints at hover but formatting and diagnostics. I use lsp-zero + null-ls + trouble. I exposed all of the keybindings on those so I can at least open my own configs for guidance. Oh yeah, having treesitter is probably a must too, and it has no keybindings on its base form.
-
Is it possible to close todo-comment/trouble's floating window after pressing enter on an item?
I am referring this as well as this this plugin.
-
Video: 5 Neovim Plugins To Improve Your Productivity
Trouble: https://github.com/folke/trouble.nvim
-
People who migrated from vscode
Trouble is so good for finding errors easily. For testing I use jest so I haven't had too many issues. What do you test with?
-
Any recommended plugins to frictionlessly see lsp references in a perhaps a popup window?
I like trouble.nvim
-
Disabling PEP diagnostics errors/warnings in LazyVim
I guess LazyVim uses https://github.com/folke/trouble.nvim for it. I should config it to not including errors regarding standardization.
lspsaga.nvim
-
What's this type of plugin called? (it shows the structure of code)
Must be lspsaga
-
Switching from Emacs. My experience
It's lspsaga. It offers a lot of UI enhancements
- Help wanted - lspsaga vs neovim/nvim-lspconfig vs mason-lspconfig - need help to understand difference
-
what plugin added the breadcrumb/context info to the winbar?
I think that's lspsaga.nvim
-
Looking for some kinda specific plugins for visibility
https://github.com/nvimdev/lspsaga.nvim shows hierarchical scope at the top of the screen. it also has a tree you can toggle at the right of the window.
-
what neovim configuration is this?
probably lspsaga?
-
How can I get the return type of a function?
Improve UI for LSP interactions https://github.com/nvimdev/lspsaga.nvim
-
Looking for a good tag browser with fuzzy find
https://github.com/nvimdev/lspsaga.nvim maybe this plugin fits your needs.
-
Blinking issue with top buffer line
Apparently https://github.com/nvimdev/lspsaga.nvim is the one adding the path and the version I prefer because removing it doesn't blink anymore but then I get the version I dislike.
-
Render links in hover documentation from LSP in Java
I found the `lsp-saga` plugin which has the above functionality built in for previews: https://github.com/nvimdev/lspsaga.nvim
What are some alternatives?
impatient.nvim - Improve startup time for Neovim
lspkind.nvim - vscode-like pictograms for neovim lsp completion items
lsp-trouble.nvim - ๐ฆ A pretty diagnostics, references, telescope results, quickfix and location list to help you solve all the trouble your code is causing. [Moved to: https://github.com/folke/trouble.nvim]
nvim-lspconfig - Quickstart configs for Nvim LSP
AutoSave.nvim - ๐งถ Automatically save your changes in NeoVim [Moved to: https://github.com/Pocco81/auto-save.nvim]
nvim-lightbulb - VSCode ๐ก for neovim's built-in LSP.
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
lspsaga.nvim - improve neovim lsp experience [Moved to: https://github.com/nvimdev/lspsaga.nvim]
lsp_signature.nvim - LSP signature hint as you type
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
renamer.nvim - VS Code-like renaming UI for Neovim, writen in Lua.