cmp-nvim-lsp VS nvim-lspconfig

For this, we need to install a new completion engine: nvim-cmp. This engine uses completion “sources” (installed as separate dependencies) to populate the completion menu. So we also need to install cmp-buffer and cmp-nvim-lsp. Check out this tutorial by TJ DeVries for more info about how this plugin works.

I use this, but there's other options: https://github.com/hrsh7th/cmp-nvim-lsp

require('lspconfig')['tsserver'].setup{

hrsh7th/cmp-nvim-lsp: nvim-cmp source for neovim builtin LSP client

You need to add nvim-cmp and cmp-nvim-lsp

I had the exact problem recently with svelte and Astro. I opened an issue that never got any reply.: https://github.com/hrsh7th/cmp-nvim-lsp/issues/56

Plugins Needed: * nvim-lspconfig * nvim-cmp * cmp-nvim-lsp

-- need to install https://github.com/hrsh7th/cmp-nvim-lsp for server in pairs(servers) do lspconfig[server].setup { on_attach = on_attach, capabilities = require("cmp_nvim_lsp").default_capabilities(), settings = servers[server], } end ```

cmp-nvim-lsp: Completion source. Shows data send by the language server.

The default capabilities are from this plugin: https://github.com/hrsh7th/cmp-nvim-lsp

cmp-nvim-lsp: integração com LSP;

Neovim (via nvim-lspconfig + mason)

Packages that we will use : blink.cmp for autocompletion, typescript-tools for the typescript LSP, neovim/nvim-lspconfig to set up the LSP, and Mason so we can install volar.

Check configs.md to ensure your language's LSP server is present there and edit the configs/lspconfig.lua file to add your language's LSP.

Neovim Install the nvim-lspconfig plugin to make configuration of the LSP client simpler. Then update your init.lua to tell Neovim which filetypes to use the language server for (i.e. .kt and .kts extensions). The LSP client will try to the start the sever by running the kotlin_language_server binary. You can directly point Neovim to the location of the binary, or include this directory in your $PATH.

👉 With LSP in this installation, I use Coc for its simplicity without the need to intervene in the Coc configuration. LSP has been very useful in my Helix modal editor to configure Helixu.

neovim/nvim-lspconfig: Quickstart configs for Nvim LSP

I suggest looking for blog posts about this, you're gunnuh wanna pick out a plugin manager and stuff. It's kind of like a package manager for neovim. You can install everything manually but usually you manually install a plugin manager and it gives you commands to manage the rest of your plugins.

These two plugins are the bare minimum in my view.

https://github.com/nvim-treesitter/nvim-treesitter

Treesitter gives you much better syntax highlighting based on a parser for a given language.

https://github.com/neovim/nvim-lspconfig

This plugin helps you connect to a given language LSP quickly with sensible defaults. You more or less pick your language from here and copy paste a snippet, and then install the relevant LSP:

https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...

For Python you'll want pylsp. For JavaScript it will depend on what frontend framework you're using, I probably can't help you there.

pylsp itself takes some plugins and you'll probably want them. https://github.com/python-lsp/python-lsp-server

Best of luck! Happy hacking.

Adding language support it neovim isn't very difficult once you're setup. I use nvim-lspconfig[1] and just about any language you could need is documented[2]. But like others have mentioned there are batteries included distributions of neovim if that's your cup of tea.

[1]: https://github.com/neovim/nvim-lspconfig/

[2]: https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...

If we can't find the basic usage in the documentation we can go to nvim-lspconfig's github repository. In there we look for a folder called server_configurations, this contains configuration files for a bunch of language servers.