.dotfiles VS nvim-lspconfig

I also did a simple script to test it out a while ago. As you might have realized, this functionality needs to listen for a few triggering characters depending on the language server, kinda like autocomplete implemented by nvim-cmp. So, I guess, until they merge the autocomplete functionality to core, this won't be added. You could, in the meanwhile, create a nvim-cmp plugin and simplify quite a bit what you already have done.

I have some here https://github.com/tiagovla/.dotfiles/tree/master/neovim/.config/nvim/lua/plugins/config/luasnip/snips . You can create contextual snippets with treesitter. Autosnipet is also an option.

I got this to work with python inlayhints https://github.com/tiagovla/.dotfiles/tree/master/neovim/.config/nvim/lua/lsp/inlay_hints and this should enable those `require("lsp.inlay_hints").setup_autocmd()`.

I'm quite happy with only texlab + nvim-cmp + luasnips. That's it. I have some snippets here https://github.com/tiagovla/.dotfiles/tree/master/neovim/.config/nvim/lua/plugins/config/luasnip/snips for latex if you need a place to start (just require the files).

I think everyone does this in their own way. I like to separate user settings and plugins in different folders inside the lua folder. And every plugin has its own config (setup, mappings, ...), so I can enable/disable them in a single place. My dots look like this.

Btw, I coded this https://github.com/tiagovla/.dotfiles/blob/0f664e30def1e460dd04fc8276f0d12f1ee2e88b/neovim/.config/nvim/lua/plugins/config/lsp/custom_servers/ltex.lua

Oh, for sure! Here you go https://github.com/tiagovla/.dotfiles

I have it in place https://github.com/tiagovla/dotfiles/blob/master/nvim/lua/plug-config/lsp/settings.lua

Do you the have the colors matched here? https://github.com/tiagovla/dotfiles/blob/master/.tmux.conf#L37-L43

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.

https://github.com/hrsh7th/nvim-cmp This is an autocompletion engine https://github.com/nvim-treesitter/nvim-treesitter This allows NeoVim to install parsing scripts so NeoVim can do things like code highlighting. https://github.com/williamboman/mason.nvim Not strictly necessary, but allows you to access a repo of LSP, install them, and configure them for without you actively messing about in config files. https://github.com/neovim/nvim-lspconfig Also not strictly necessary, but vastly simplifies LSP setup. https://github.com/williamboman/mason-lspconfig.nvim This lets the above two plugins talk to each other more easily.

This specific issue talks about fixing clangd for that error: https://github.com/neovim/nvim-lspconfig/issues/2184. The issue is ongoing for ccls AFAIK but for clangd, this has been discussed and fixed in the past already.

I am trying to set up the pbkit language server for protobuf files. Since it is not part of the nvim-lspconfig repo's server configurations, I have to figure the way out myself. It doesn't seem to be too difficult, as I can start from the bufls configuration there. The following is what I have at the moment:

I have configured neovim with lspconfig and mason. Added the suggested configuration of the lsp config(https://github.com/neovim/nvim-lspconfig) to ~/.config/nvim/after/plugin/lsp.lua Then I installed via mason the following language servers:

Personally, i think nvim-lint is the best alternative currently, specially so because it has no dependencies on external binaries. This guide assumes you already have your LSP set up with nvim-lspconfig (or an alternative like lsp-zero). You should also have an way to install the linters you are gonna need, i highly recommend Mason with mason-lspconfig.

Basically neovim can act as a client to a variety of different language servers (https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...) which give neovim IDE capabilities. This can be done in original Vim also but requires external plugins which can be a pain to compile and install. Neovim has it built in.

I'm struggling to get [sqlls](https://github.com/joe-re/sql-language-server) with [nvim-lspconfig](https://github.com/neovim/nvim-lspconfig) to use Postgres syntax.