nvim-lspconfig

It's documented here (with migration steps): https://github.com/neovim/nvim-lspconfig#important-%EF%B8%8F and in a pinned issue. and nvim-lspconfig :help has a migration guide: https://github.com/neovim/nvim-lspconfig/blob/16812abf0e8d81...

Nvim 0.12 (prerelease) also has ghost text with the "textDocument/inlineCompletion" LSP server capability[1]. Currently supported by the "copilot" config[2], but any LS that supports "textDocument/inlineCompletion" can be used (and the config[2] shows optional QoL improvements). 1: https://github.com/neovim/neovim/pull/33972 2: https://github.com/neovim/nvim-lspconfig/pull/4029

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 use it to install 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. It's much more robust than the regex-based default highlighting. https://github.com/neovim/nvim-lspconfig This plugin helps you connect to a given language LSP quickly with sensible defaults so you can get IDE features. You'll still need to install the LSP though. https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser... For Python you'll want pylsp. For JavaScript

Adding language support in 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...

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 see where you're coming from. FWIW, I've been using Neovim for an odd 7 years or so and only use plugins where absolutely necessary. I'll usually just add an appropriate BufWritePost (trigger after saving the buffer) autocommand for the language's file extension that does what I want. Or I'll add a keybind in .config/nvim/ftplugin/<lang>.vim (or <lang>.lua). You can do fancier stuff with plugins but I find that I just don't need it (and you probably don't either, by the looks of it). The default LSP client config at https://github.com/neovim/nvim-lspconfig#suggested-configura... sets everything up for you, if you're using an LSP server. I'm not sure why it hasn't been merged into the Neovim repo; possibly because they want to keep the editor core fast and minimal. All this means you have to do a little more configuring than with somethi

nvim is in my setup scripts with dotfiles and is picking up my vim config per my init.vim. But still - look about actual setting up it [1], [2], where [1] stragight says "if you need autocomplete, you need plugin for that". I obviously can do it, but I just don't want to... Batteries should be included in $CURRENT_YEAR. It is probably missed, but I use vim everyday, as text editor for many years. My .vimrc on github is 3 years old, and only because I moved it there from bitbucket and didn't bothered to preserve history. I'm not against it. It was that original comment that I answered, was saying that vim is effective/better for IDE specific tasks (e.g. large refactorings, that inititial comment that I've replied), and after many years of using vim I strongly believe is rather ignorant and shows not understanding of power and features of m

Yes. https://github.com/neoclide/coc.nvim Or https://github.com/neovim/nvim-lspconfig https://github.com/hrsh7th/nvim-cmp No different than installing plugins in VSCode for completions, they all work via calling out to a LSP server using https://microsoft.github.io/language-server-protocol/ When you don't understand something it's only natural to be unaware of its capabilities, yes.

In the case of Free Pascal, may I remind you that there is a fully featured IDE called Lazarus… That’s cool, but if you already use Neovim for other things, there’s a Free Pascal Language Server Protocol (LSP) server for it too [1]. You’ll many of the same features that Lazarus has, like code completion, diagnostics, etc. In fact, it’s the same LSP that’s available for VS Code [2] and it uses Lazarus as a backend. Too much is being made about how hard Neovim is to configure; if you’re new to it or to Lua, just use LSP Zero [3] that takes care of all of the details of installing LSP, linters, etc. [1]: https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser... [2]: https://github.com/genericptr/pascal-language-server [3]: https://github.com/VonHeikemen/lsp-zero.nvim

And the vim modal editing pattern is nice for a basic text editor but has pretty poor extensibility… Nothing could be further from the truth. There are tons of plugins, scripts, tutorials for literally every scenario you can imagine since Vim has (never mind its predecessor Vi) has been around since 1991. at some point you just can't do everything with single letters, you need actual, complex commands Vim’s power is its composability. Once you understand text objects (word, sentences, paragraphs) and motions, you can do anything you want. If you need to repeat a string of commands together, you can record macros on the fly, create an autocommand or a plugin if that’s what needed. Neovim in particular has LSP support built-in, which gives the editor semantic knowledge of your code, just like an IDE. So renaming, refactoring, formatting, sy

> vi/vim is nice but I find the convenience of VSCode - auto complete, show inf doc etc - very useful You can have all of that on vim. On neovim, you can even setup LSP with the same LSP servers that VSCode uses [1]. The learning curve is steeper but if you like vim/neovim keyboard-centric features, it is worth it. The only thing I miss from VSCode is maybe the debugger, not because you can't have one, but because it is a bit tedious to set it up and more error prone. So sometimes I use VSCode as a debugger, but I'm pretty happy with my config on neovim (imports, auto complete, docs info (or "hovering"), definitions, go to definition, rename a symbol, etc., you can have all of that with LSP). [1] https://github.com/neovim/nvim-lspconfig

It connects to a community maintained lsp server that wraps tsserver https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...

> Why can't arbitrary LSP clients connect directly to tsserver (maintained by MS) ? As far as I'm informed, they can. For example, NeoVim language client has a pretty wide range of officially supported servers [0], including tsserver. [0] https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...

> And neovim is heavily embracing the LSP paradigm, where you'd use something like gd to jump to definition when on top of a function and a language specific LSP server will tell Neovim where to jump to. This x100. I switched to neovim+pylsp a few months ago, and it's been an absolute delight. I use lspconfig [1] and pyslp [2] since most of my time is spent developing Python code. Not only can I navigate more quickly and easily, I also find myself catching more silly errors before run-time due to better linting from the lsp. It used to be that I wouldn't use vim beyond quick edits on single files. Although I still prefer to use vim style bindings in IDEs, I can go much further before I feel the need to fire up an IDE in the first place. [1]: https://github.com/neovim/nvim-lspconfig [2]: https://github.com/python-lsp/python-lsp-server

If you haven't tried again recently the neovim team has done a ton of work updating the documentation on nvim-lspconfig [1]. There's also projects like kickstart.nvim [2] which aim to provide a very simple starting point for new users. It's "batteries-included" neovim which notably includes LSP, TreeSitter, completion engines, and some basic git functionality. [1] https://github.com/neovim/nvim-lspconfig [2] https://github.com/nvim-lua/kickstart.nvim