coc-clangd VS coc.nvim

C/C++/Objective-C

I use coc.nvim with coc-clangd

I am currently using coc-clangd(https://github.com/clangd/coc-clangd) for c++ syntax highlighting. I use for coding sometimes, and I get an error because is only g++ header, not for clang. What should I do?

Using this plugin I have installed several extensions like coc-clangd and coc-rust-analyzer .

I don’t mean to be rude but, what about checking ‘configuration’ section: https://github.com/clangd/coc-clangd

use plugins. I prefer coc.nvim paired with coc-clangd Clangd is what CLion uses under-the-hood for a lot of its autocomplete/linting/etc., so this pair gets you fairly close. (you miss out on CLion's proprietary additions and AI completion, but for quick work or places CLion is too heavy, its great)

Not sure about setting up on OpenVMS, but I've been getting along with simple C/C++ projects with coc-clangd which was very easy to set up.

I forgot to mention before, with coc.vim, you will need https://github.com/clangd/coc-clangd to integrated c++

Thanks! I read about using LSP/Clangd with vim via [coc](https://github.com/clangd/coc-clangd) and I think that's the path I'll try going down.

Other responses, thanks for your input. Just want to clarify that I have tried VS and VSCode with limited success (sometimes search works, sometimes it doesn't, and my biggest gripe is an occasional lack of transparency into what's going on under the cover).

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

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