vim-lsp-ale VS vim-lsp-settings

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.

I am reading here but still... it seems all OK. It is weird that it was working with ALE with the current setup. Anyway, I noticed that every once in a while I get this error when I change buffer.

There's https://github.com/mattn/vim-lsp-settings to save even more lines, which is I think what OP wants.

vim-lsp-settings makes installing lsp for vim-lsp trivial: :LspInstallServer

Hello everyone, I have this problem when using vim-lsp-settings, that every time my cursor passes through a word (sorry I don't have enough information to derive what type of word, but take Type, Function in Python, or constants (like g:lsp_diagnostics_signs_enabled) and has() in vimrc) it always showing similar occurrences of the word, and I don't want that. Not only it takes some time (highlighting that word cursor is on, and when moving cursor really fast it couldn't catch up), it's usually something I don't really need (well, if it could be configured to be faster and my laptop won't screeching then I'm all in - I'm using thinkPad x270).

I use vim-lsp plugin which only needs a few lines of config. It has several JavaScript language servers listed in vim-lsp-settings.

Then lsp. All four of these: prabirshrestha/vim-lsp; mattn/vim-lsp-settings; prabirshrestha/asyncomplete.vim; prabirshrestha/asyncomplete-lsp.vim

vim-lsp that can be bootstrapped with vim-lsp-settings, for jumping to definitions, etc.