diagnostic-languageserver VS nvim-lint

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.

Personally, i think nvim-lint is the best alternative currently, specially so because it has no dependencies on external binaries. This guide assumes you already have your LSP set up with nvim-lspconfig (or an alternative like lsp-zero). You should also have an way to install the linters you are gonna need, i highly recommend Mason with mason-lspconfig.

Try out https://github.com/mfussenegger/nvim-lint for linting tools, it integrates with nvim diagnostics module, might cover all use cases of null-ls for someone shopping around.

People looking for alternative can check these projects: - nvim-lint - formatter.nvim

For linting, I would recommend nvim-lint. Again the same step as before, a little bit of setup code to register your linter and you're good to go!

This will be the third linting solution to make use of the [Neovim Diagnostic] module after null-ls and nvim-lint. All can co-exist, all have the pros and cons.

I use nvim-lint (https://github.com/mfussenegger/nvim-lint), but I still don't know exactly how to achieve your goals with it. My hunch is that it should be somewhat straightforward, since Lua code could be used to provide the executable command (i.e. if in poetry project then cmd =poetry run ...else if ... then ... end)

It's not obvious from the website, but this is the blog of GitHub user @mfussenegger, who is a Neovim core member, one of the primary maintainers of Neovim's LSP client implementation, and the other of several excellent plugins.

https://github.com/mfussenegger/nvim-lint works with the diagnostics API that was created after LSP was added, to allow non-LSP to use diagnostics API. Meaning you can see LSP and linting in the same interfaces if you use this API.

As part of my work-in-progress Neovim [plugin]([https://github.com/nat-418/tcl.nvim)(https://github.com/nat-418/tcl.nvim)) for Tcl development, I added support for Nagelfar syntax checking in the nvim-lint plugin. This provides inline checking for errors as seen in the attached screenshot. If anyone has any ideas on how to create a Tcl Language Server, or knows of a project already working on one, I would be very interested to know about it.