diaglist.nvim
lspsaga.nvim
| diaglist.nvim | lspsaga.nvim | |
|---|---|---|
| 1 | 64 | |
| 173 | 2,697 | |
| - | - | |
| 0.0 | 9.3 | |
| over 1 year ago | about 1 year 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.
diaglist.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?
lsp-status.nvim - Utility functions for getting diagnostic status and progress messages from LSP servers, for use in the Neovim statusline
nvim-lspconfig - Quickstart configs for Nvim LSP
nvim-navic - Simple winbar/statusline plugin that shows your current code context
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 🦍
nvim-lightbulb - VSCode 💡 for neovim's built-in LSP.
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
lsp_signature.nvim - LSP signature hint as you type
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
trouble.nvim - 🚦 A pretty diagnostics, references, telescope results, quickfix and location list to help you solve all the trouble your code is causing.
nvim-compe - Auto completion Lua plugin for nvim
lspkind.nvim - vscode-like pictograms for neovim lsp completion items
vim-floaterm - :computer: Terminal manager for (neo)vim