doom-nvim VS coc-clangd

DoomNvim

The vue config is pretty complex because we initialise 3 different instances of volar lsp that have different responsibilities to improve responsiveness (same as VScode extension) but there are much simpler examples i.e. rust

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