lspsaga.nvim
diagnostic-languageserver
lspsaga.nvim | diagnostic-languageserver | |
---|---|---|
64 | 16 | |
2,697 | 406 | |
- | - | |
9.3 | 1.6 | |
about 1 year ago | 3 months ago | |
Lua | TypeScript | |
MIT License | 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.
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.
diagnostic-languageserver
-
Vim - Using clippy as a linter
I'm not using the rust-analyzer plugin actually. I'm using the system installed rust-analyzer and diagnostic-language-server which integrates it with vim. Is there a flag or something to make rust-analyzer return clippy results as well?
-
diagnosticls-configs-nvim - pre-defined linter and formatter configs for diagnostic-languageserver
For those who use diagnostic-languageserver, this plugin provides a list of pre-defined configurations for you to use without the hassle to figure out the config on your own. Making it easier to integrate with less code.
- How to determine which linter is currently being used?
-
Eslint Lua Solution?
So reading through everyones suggestions it seems like diagnosticls is the way to go. Looks like this is the official neovim solution https://github.com/iamcco/diagnostic-languageserver formerly https://github.com/nvim-lua/diagnostic-nvim
-
Config to edit bash scripts with fancy LSP features, linting and formatting
Does anybody have such? Maybe you could share your experience? I use coc.nvim. My eyes fell on these 3 tools. The first one is language server and it has coc extensions coc-sh. But others are not so I am not sure which vim plugin should I use to hook them up: besides diagnostic-languageserver there are syntastic and neomake - bash-language-server - shellcheck - shfmt
-
Neovim LSP and typescript
>https://github.com/iamcco/diagnostic-languageserver
-
TypeScript: ESLint code actions and (experimental) diagnostics / formatting
I also added 2 experimental features designed to reduce the amount of boilerplate required to get a functional TypeScript development environment. diagnostic-languageserver and efm-langserver are powerful, but they can be tough to set up for new users, so I wanted to implement low-config, out-of-the-box alternatives for formatting and linting:
-
Losing my mind with formatting
I’ve personally never gotten efm to work at all, and I never figured out why (much like your situation). I use diagnostic-languageserver, which worked like a charm the first time. I’ve heard some users say it’s slower (TypeScript versus Go), but I’ve never had any speed issues.
-
Neovim - Why I'm switching to Native LSP over CoC
Aside from that, the biggest difference versus CoC is the ecosystem, which affects setup / tweaking time and code actions. I was able to set up ESLint diagnostics with diagnostic-languageserver, but it doesn't integrate with typescript-language-server at all, and I haven't been able to set up ESLint fixing + Prettier, either, All of that is trivial with CoC.
-
LSP and pylama…
Some LSP like diagnostic language server and efm language server do that for you. However, you will need to do some manual setup yourself for pylama to work with them, unfortunately, I don't see either of them have an example for pylama so you will have to write one yourself for those LSP servers.
What are some alternatives?
nvim-lspconfig - Quickstart configs for Nvim LSP
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
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.
efm-langserver - General purpose Language Server
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
coc-spell-checker - A basic spell checker that works well with camelCase code for (Neo)vim
lsp_signature.nvim - LSP signature hint as you type
neomake - Asynchronous linting and make framework for Neovim/Vim
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
syntastic - Syntax checking hacks for vim