nvim-lspinstall VS diagnostic-languageserver

A word of caution, I believe lspinstall has been deprecated in favor of nvim-lspinstall which itself has also been deprecated in favor of mason-lspconfig

kabouzeid/nvim-lspinstall will aide in installing lsp's if you want. I have chosen not to because I want to have my full setup scripted so when I setup any new machine I just run my ansible-playbook. This library is nice to just set things up quick and play with them.

nvim-lspinstall

I'm trying to edit a lua file, and got this error which I realize is because I didn't have the Lua language server installed. So using the LspInstall plugin, I did :LspInstall lua which was successful.

Once you have it installed, you can configure it following the configuration of this file: https://github.com/kabouzeid/nvim-lspinstall/wiki. The part that ia bellow the comment "-- lsp-install" works and it was what I used initially when I didn't really know much about configuring neovim.

I am using lspinstall to install language server. It uses this json-language-server. As the docs says jsonc is supported and it allows comments in jsonc filetypes but the lsp is not showing diagnostic if I make any other syntax error. On line 34 i have removed a comma and still lsp showing no diagnostic error in jsonc file.

You could try to use the instructions that nvim-lspinstall uses to install the tailwindcss language server: https://github.com/kabouzeid/nvim-lspinstall/blob/main/lua/lspinstall/servers/tailwindcss.lua (lines 4 - 12)

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?

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.

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

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

>https://github.com/iamcco/diagnostic-languageserver

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:

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.

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.

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.