plugin-template.nvim VS vim-lsp

I was put off by the complexity of adding tests but in the add I got it setup in my plugin by downloading a plugin template and copying the way everything is done. Probably this one https://github.com/m00qek/plugin-template.nvim

Hey, I have put together a template for Neovim plugins that proposes a structure and have a good setup for tests. Take a look, it might inspire you https://github.com/m00qek/plugin-template.nvim

Hello everyone, I created a plugin template for Neovim before and now I'm planning to add a general guidelines section to its documentation. To not make this too personal I'd like to hear from you what are good tips, guidelines, do/don't, etc. when writing a Lua plugin. Does anyone here have strong opinions on this?

I suggest you to add some tests to it, which will ensure that it keeps working when you add more stuff to if in the future. One way is to do setup them like in https://github.com/m00qek/plugin-template.nvim

I had the same trouble recently so I put together a template with the solution I found: https://github.com/m00qek/plugin-template.nvim

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).