unix-as-ide VS nvim-lspconfig

> I've never understood why people and to extend vim to try to make it half of an IDE.

Because vim ships with on any *nix machine and provides a consistent experience no matter where you use it.

Vim is the DE part and people add plugins or whatever to enrich the text editing experience with LSPs or other language aware plugins, and the I in IDE is in the form of the integration with the tooling already available.

This[0] might shed some better light on the "why"

[0] https://blog.sanctum.geek.nz/series/unix-as-ide/

Check out “UNIX as an IDE”. First Google hit; https://blog.sanctum.geek.nz/series/unix-as-ide/ There are some great talks on YouTube but can’t be bothered to search :)

I use the CLI as my IDE. For me, that's FreeBSD or OpenBSD most of the time with a little bit of Linux (and as little Windows as possible). I usually wrap it all in a tmux session, but with vim/neovim offering :terminal functionality these days, I could see an alternate universe where that got flipped/inverted.

See Unix as IDE for an example.

I choose vim/neovim because I need a "just" code editor, and also it can be easily leverage my tools capabilities on UNIX way, and you can read more on this article Unix as an IDE, but the all-in-solutions, like an IDE, is not the right tool for code editing, it came with a lot of features and defaults that you in most cases I don't need it, or I have to learn how to use them according to that IDE.

Your teacher probably subscribes to the idea of Unix as an IDE, and I do too! It's important IMO to avoid holy wars, but there are some spectacular tools built into your Unix computer if you take the time to get to know them.

Vim is first and foremost a text-editor. In the Unix philosophy other tools should fill the places of the functionality a fully-fledged IDE gives you. You can add plugins and heavily craft your .vimrc to make it a lot like an IDE. But that's not really the "unix way" so to speak. I'm not necessarily some sort of coding elitist. I'll settle for other tools when I have to. I've also spent more hours than I care to admit making VIM more or less an IDE. But there is a sort of simplicity in being able to develop remotely in a test environment using vim and few other CLI tools. I recommend checking out Unix as and IDE for an intro to what I'm talking about.

Yes, this helped me https://blog.sanctum.geek.nz/series/unix-as-ide/

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.