dotfiles VS vim-lsp

Didn't think I'll see another user with a similar config than mine. I also use ALE + nvim-lsp + ddc. So you can have a look at my config and feel free to DM me with your concerns.

My nightly config with ddc in lua

Also here is my galaxyline code if you want to take a look at it: https://github.com/creativenull/dotfiles/blob/8d1840a30265963aef71458363ccd621969b86b2/.config/nvim-nightly/lua/cnull/statusline.lua

But since you are in lua you will have to evaluate the lua inside vim which is then passed on as a string (kinda complicated to explain, code is a bit clearer), I did something similar with my status line, although a bit more minimal which you can take a look at it here.

I'm not sure what issues you're having with it, it should run all the linters and fixers automatically without any configuration needed to add in your config, besides adding the plugin. :ALEInfo is a great place to look at to see whats enabled and working. I like a bit control so i disable the automatic running and turn on only the linter/formatter I need on a filetype basis (aka add then to after/ftplugin), you can take a look at my dotfiles and see how I have them setup.

I've had the same issue, I just had to change the find_command key in the find_files function on telescope and create a different keymap to call it, you can take a look at my telescope setup

So what you really want, is to merge those two tables together, you can have a look at how I do it in my nvim lsp config but for your code it could be:

Has anybody managed or got an idea how to make SonarLint Language Server work with e.g. vim-lsp?

You need to configure a language server. For C++ it's a bit tricky, so good luck with Go. There are other plugins that provide semantic highlighting using LSP, for example https://github.com/prabirshrestha/vim-lsp (I didn't try it, but it seems good).

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.

I feel the same way. Not a one-liner but the smallest config LSP plugin I've found is vim-lsp. It works in both Vim and Neovim.

The only major feature that Neovim still has is a built in LSP client. But I find the built in Neovim LSP client is unusably buggy, you're much better off using any of the other LSP plugins. What I use is vim-lsp, but I've tried all of the major lsp client, they are all significantly better than the built in Neovim LSP.

As for install/configuration, all you need is the latest Vim, the plugins I mentioned, and that bit in your vimrc. You can do a bit better than that if you copy the entire config with mappings from the vim-lsp GitHub page.

I have a problem with Deoplete and Vim-LSP completion (Python's Pylsp and Jedi-Language-Server). The suggestion is much less, and it also misses a lot of opportunities to suggest compared to Deoplete-Jedi, which literally defeats the former by a large margin. Is there a setting to make this duo works like deoplete with deoplete-jedi?

- add the [prabirshrestha/vim-lsp](https://github.com/prabirshrestha/vim-lsp) plugin and config to your `.vimrc` (note: `pylsp` is *not* necessary).