cmake4vim VS coc.nvim

The plugin is here and adds features like kits, customizable build types, support for running ctest, automatic updates/restarts of clangd LSP server and also provides some functions that allow cool plugin customization. Basically, you get features that are mostly equivalent with features from the plugin I used in vim, but implemented in Lua. Feel free to test it out. Note that I only tested it on my machine (M1Pro mac) and in one Linux container, so expect bugs, crashes and various errors. Feel free to post issues and PRs with fixes.

The plugin depends on cmake4vim (a plugin for CMake integration with Vim/Neovim), this allowed to have deeper integration of gtest-vim for CMake projects (you can just switch between CMake targets in order to run different tests).

Around the year ago, I have posted the last post about cmake4vim plugin updates.

CMake integration: https://github.com/ilyachur/cmake4vim

Not sure if you want to add a other plugin, but I've had good results with cmake4vim. It integrates with Dispatch if it's installed.

Good question! And for Cmake projects I really like the cmake4vim plugin from ilyachur. https://github.com/ilyachur/cmake4vim

I think, that you can do such 'advanced' features without used plugins. Concerning my C++ workflow, I'm using it with Cmake and https://github.com/ilyachur/cmake4vim plugin adds the possibility to compile it in a few commands. Also, I've added a feature to run the CMake target with the use of one command and hope, that soon it will be merged.

Here is the issue with the video https://github.com/ilyachur/cmake4vim/issues/68

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.

When you install an extension it runs an npm install or yarn, iirc, which is going to be problematic for you being offline. I was going to say you could copy that ~/.config/coc folder directly to the other machine but yeah, Windows, no idea. You see here https://github.com/neoclide/coc.nvim/wiki/Using-coc-extensions

You can try https://github.com/neoclide/coc.nvim, the pre-requisite is to install nodeJS, then to install all the languages LSP. This works for me for Angular, Rust, JavaScript, Vimscript, etc