LanguageClient-neovim VS vim-lsp-ale

i know the language client neovim has such a function (:help languageclient_textdocument_codelens after compiling its helptags). AFAIK you can get that running in Vim 8, but not sure.

On NeoVim, the built-in LSP client works without modification. On Vim, you will need LanguageClient-neovim.

I'm using LanguageClient-neovim. Here's the relevant portions of my init.vim:

I just saw a nice post in /u/medwatt about using vim for VHDL/Verilog and thought I'd contribute a little! * Syntax and error highlight: https://github.com/autozimu/LanguageClient-neovim * Column align: https://github.com/junegunn/vim-easy-align * Remove annoying whitespaces: https://github.com/ntpeters/vim-better-whitespace * Partial (fuzzy) filename search: https://github.com/junegunn/fzf.vim * Outline all declarations inside a file: ⠀https://github.com/preservim/tagbar * Treat indentations as vim-objects (useful for languages that don't use { }): https://github.com/michaeljsmith/vim-indent-object There is also mouse support in vim for those who want it. Try typing :set mouse=a. Very useful for resizing windows. I also highly recommend you get good at using folds (https://vim.fandom.com/wiki/Folding). It makes it a LOT easier to navigate files. You can save your fold config per-file with :mkview and load it later with :loadview. If I come up with more hints - I'll mention them in the comments!

I've been using LanguageClient and solargraph gem with plain Vim 8 for a long time already. Still, having a bit better experience at Ruby coding with Emacs and its lsp-mode & company & inf-ruby combo.

Might migrate to Neovim's native LSP support at some point, however I find vim-lsp more feature complete out of the box. I used to use LanguageClient-neovim, however, I missed proper support for signature help.

YCM is a client. The client is a plugin for Vim or Neovim, even the "built-in" client in Neovim is just a Lua plugin that is included with the editor, it's not really built-in. Examples of other clients:LanguageClient-neovim, vim-lsp, ale.

LanguageClient-neovim just merged some support for semantic tokens and the plan, as I read the PR/issues, is to next implement some default mappings from the semantic tokens to highlight groups.

The best LSP client is the one that works for you. When it comes to neovim, there is a generous variety of LSP clients to choose from. The notables ones being vim-lsc and vim-lsp written in vimscript, LanguageClient-neovim written in rust, YouCompleteMe is written in python and in my experience is the hardest to install, coc.nvim written in typescript and, of course, the neovim's built-in one. I would recommend going with coc.nvim, as it is the best LSP client right now, though it provides much more features than a standard lsp client does and for some people it is a disadvantage and for the others it's not. Also you have to install node.js on your system for coc.nvim to work. I myself use neovim built-in one for a few reasons: it's not in stable yet, but when the neovim 0.5 version comes out, it is gonna be the standard client. Another reason is it's extremely lightweight and customizable. There were already several discussions on the subreddit about the clients you can check out.

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.