ideavim VS nvim-lspconfig

[this neovim plugin](https://github.com/abecodes/tabout.nvim) helps me get out of double quotes and parenthesis while being in insert mode (I use [ideavim](https://github.com/JetBrains/ideavim/)). The present implementation of this behaviour in the IDE as [smart keys](https://www.jetbrains.com/help/idea/settings-smart-keys.html) isn't cutting it for me.

IntelliJ with Vim bindings is really good! It is actively supported so patches come often to fix some discrepancies with the original software. It even supports a handful of plugins out of the box.

" https://github.com/JetBrains/ideavim/wiki/IdeaVim-Plugins set clipboard+=unnamed set clipboard+=ideaput set ideajoin set idearefactormode=keep set incsearch " set relativenumber set showmode set hlsearch set surround set visualbell set commentary set highlightedyank set argtextobj set matchit set multiple-cursors " requires easymotion and ace-jump plugins set easymotion " requires quickscope plugin set quickscope

For partial chest hair, use IdeaVim

The biggest advantage of vim is the movements (key bindings), and there are plugins for many editors for that, e.g. https://github.com/JetBrains/ideavim

There are many apps, web sites, IDE plugins, and extensions that have vim keybindings. You can use vim keybindings all the time, everywhere.

There is a nerdtree plugin for ideavim https://github.com/JetBrains/ideavim/wiki/NERDTree-support

ideavim has vimscript, but I am not sure how "full" it is, never tried.

IntelliJ IDEA makes it definitively easy to start without setting things up. IdeaVim makes it better for a Vim user. But also frustrating, as certain Vim-features don't work.

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.