trouble.nvim
lspsaga.nvim
trouble.nvim | lspsaga.nvim | |
---|---|---|
60 | 64 | |
5,687 | 2,697 | |
- | - | |
9.5 | 9.3 | |
16 days ago | over 1 year 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
-
My Flow and Productivity has Improved with the Simplicity of Neovim
In a similar spirit to Outline, there is a plugin called Trouble. This was created and maintained by the creator of LazyVim as well. Think of Trouble as having two functions for me.
-
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
lspsaga.nvim
- [Neovim] Quels plugins dois-je utiliser avec le LSP intégré?
-
winbar below lualine buffers
Just like this? If yes, you can try lspsaga.nvim, nvim-navic, or barbecue.nvim.
-
Cannot find setting to get linter errors on type with Rust Analyzer
I am not 100% sure if that is what he is using but you can achieve the same thing using Lspsaga, specifically the on_insert and on_insert_follow options
-
Ideas to practice lua and neovim plugin development
Participating — I'd like to see more contributors for LSP Saga, the various ChatGPT plugins, and pets!
-
Any recommended plugins to frictionlessly see lsp references in a perhaps a popup window?
Maybe Lspsaga could help
-
Is it possible to see peek the documentation for a symbol within an LSP hover window?
I think the LspSaga plugin has a hover_doc function! it's been really useful for me :D
-
Has anyone encountered this buf error in lspsaga when working with svelte files?
Yo, good question.. Yes i have. It's actually working now i filed an issue on lspsaga and the owner created a quick fix for it: https://github.com/glepnir/lspsaga.nvim/issues/866
-
How do I get this little tree like hierarchy of the code on the top?
You might like this: https://github.com/glepnir/lspsaga.nvim.
-
[ HELP ] - LSPsaga hover window stuck
I already did, but you closed it 🫡 here is the link
-
My lspsaga's lsp_finder will cause weird behavior
Did you post an issue on GitHub? The library author has been exceptionally quick to respond to bugs and reports like this in my experience.
What are some alternatives?
impatient.nvim - Improve startup time for Neovim
nvim-lspconfig - Quickstart configs for Nvim LSP
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]
navigator.lua - Code analysis & navigation plugin for Neovim. Navigate codes like a breeze🎐 Exploring LSP and 🌲Treesitter symbols a piece of 🍰 Take control like a boss 🦍
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.
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
lspsaga.nvim - improve neovim lsp experience
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.