cmake4vim VS vimspector

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

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.