nvim-ale-diagnostic VS vim-lsp-ale

I did find nathanmsmith/nvim-ale-diagnostic but it is abandoned; and I'm not sure if it accomplishes what I want.

I didn't replace it, but started using https://github.com/nathanmsmith/nvim-ale-diagnostic instead. With a few tweaks works quite well, but long term I'm planning to move to null-ls and/or efm.

My current setup is: use ale for linting and formatting with https://github.com/nathunsmitty/nvim-ale-diagnostic to send lsp diagnostics to it.

To use it with nvim-lsp you will need nvim-ale-diagnostic

I just use this plugin and toggle ALE itself.

for folks who are on nvim-lsp there is a similar plugin nvim-ale-diagnostic

ALE can use LSP as well. And if you are using vim-lsp, you can use the same instance of server for both with vim-lsp-ale bridge plugin.

Don't you need vim-lsp-ale for that? It puts lint results from vim-lsp into ALE's interface so ALE doesn't need to run a second lsp server. Which seems to be another way of saying ALE uses it as a source.

However; apparently this causes two LSP's to run. Instead of nvim's default lsp; there is also prabirshrestha/vim-lsp and mattn/vim-lsp-settings that runs LSP's. There is rhysd/vim-lsp-ale to fix the concurrent LSP running between Ale and vim-lsp, and shun/ddc-vim-lsp which integrates vim-lsp with ddc.vim

See comment here for a setup with vim-lsp. Add ale for lint support and vim-lsp-ale to put lsp linting into ale.

ALE is primarily for linting (although it may also serve as basic LSP client). The protocol itself is for code completion, hover tips, navigation, workspace symbols, finding references, highlighting, renaming, reformatting, refactoring etc. And also diagnostics (which you can integrate with ALE via vim-lsp-ale).

I looked at this earlier and was unsure if this is in lieu of ALE or in addition to ALE. I saw a post about also needed - How can I use ALE and vim-lsp together? When I looked into vim-lsp-ale I was unsure about how to configure PLS for perl.

Try vim-lsp-ale to get vim-lsp lint errors to show in ale. You should turn off all other linters unless you actually need them.

Sorry I should have mentioned I'm using ALE for linting/fixing. Would I have to remove ALE to use Neovim's native LSP, or use a plug-in like this I'm assuming?

To me "integrated" means I do everything from one application -- no building in the shell etc. I think the biggest knock against "integrated" is when vim plugins don't work together (like ale and lsp before vim-lsp-ale).

Hello! I thought I'd mention this plugin to people, as people might not know about it. rhysd on GitHub has put together a plugin that connects vim-lsp to ALE, completely without much, if any, help from me. I think it's pretty cool, and it could be useful for someone. Check it out.