nvim-cmp VS coc.nvim

If you use Neovim and haven’t tried nvim-cmp, start here.  It’s the de-facto completion framework, written in Lua, feeding on LSP, path, buffer, snippet, and AI sources.  Everything in the popup—icons, ghost text, documentation windows—is customizable, and its community drives dozens of extension sources.

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.

👉 NVIM-CMP toolkit for better control comfort nvim. Such as help, command completion and much more.

You should use many source plugins to use nvim-cmp effectively. The orders to load them lazily are difficult a bit to understand.

nvim-cmp (A completion engine plugin for neovim written in Lua. Completion sources are installed from external repositories and "sourced".)

hrsh7th/nvim-cmp: A completion plugin for neovim coded in Lua.

Like many using Neovim, I'm leveraging the Nvim-Cmp plugin. With this plugin, I get the snippets, code completion, and documentation on functions that I'm used to that help me out when my brain slows.

Doing a fast scan on the commit history this is probably related to https://github.com/hrsh7th/nvim-cmp/pull/1689 . Hope it helps.

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.

Neovim comes with a client. For Vim you will need to install one, such as CoC, LanguageClient-neovim, or vim-lsp.

👉 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.

As well as its own plugins Vim/NeoVim can use VSCode's LSPs, DAPs and extensions either directly or via plugins like CoC[1] and Mason[2].

I would be surprised if emacs couldn't do the same.

1. https://github.com/neoclide/coc.nvim

The most famous TypeScript one probably is coc.nvim

It is flatly the wrong mindset to think of vim as an IDE. vim is a code editor: get in, make change, get out. Consider vim koans, which are a fun little read. You can throw coc.nvim at Neovim, along with a few other bits to give you a Good Enough setup, but vim isn't and will never be an IDE.

I just did a fresh reinstall of CoC, on a newer version of Neovim. I'm now seeing something I hadn't seen before, which CoC calls "inlay hints". They look like this:

I'm currently on an old setup (using coc and polyglot) and nvim v0.6.1. I'll be updating to a more modern setup within next year, using the native lsp and building nvim more frequently. But that's not today.

coc.nvim

There are some plugins which have the best documentations I have ever seen, but you need to read it from the Vim.

Example of coc.nvim: https://github.com/neoclide/coc.nvim/blob/master/doc/coc.txt

Actually you can with coc.nvim & coc-sh. So long as shellcheck is also installed and in PATH, it'll integrate with coc/vim just fine.