coc-clangd VS vimspector

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

There are DAP extensions for both Vim (e.g. https://github.com/puremourning/vimspector) and NeoVim (https://github.com/mfussenegger/nvim-dap). I can't speak as to the experience in detail (I think I briefly played with nvim-dap a year or two ago), but I suspect that for most it will be good enough.

I struggle a bit to put what i want into words but i still try my best.So i got some plugins likehttps://github.com/sindrets/diffview.nvimhttps://github.com/harrisoncramer/gitlab.nvimhttps://github.com/puremourning/vimspectorand so on (but those are the one which i need that "feature" the most).

The actual title is "Vimspector - A multi-language debugging plugin for Vim".

It is a UI around DAP: https://github.com/puremourning/vimspector#what-vimspector-i...

vimspector

I do think VSCode is a great tool and I recommend it frequently to people, but I still want to set the record straight here. Yes, vim is obviously limited in the sense that as a CLI app it doesn't draw it's own PDF or HTML windows, that's fair. But it can remote control your favorite PDF viewer or browser for roughly the same functionality. I'm currently writing my thesis using vimtex and it's quite smooth. And all the other stuff you mention is implemented quite competently by various plugins like vim-fugitive, coc.nvim, vimspector and copilot.vim.

You could try vimspector. It's main target is vim and not neovim.

https://github.com/puremourning/vimspector/

I use vim for C++ coding, however it is a bit difficult to set up to make it productive. I use YouCompleteMe [0] for autocompletion, Vimspector [1] with the C++ plugin for debugging, ALE [2] for linting, along with a few other general plugins (such as NerdTREE for file view).

[0] https://github.com/ycm-core/YouCompleteMe

[1] https://github.com/puremourning/vimspector

[2] https://github.com/dense-analysis/ale

For debugging normally I'd throw a breakpoint() and then have it launch pdb in a terminal from within nvim, but vimspector also exists if you'd rather.