DAPInstall.nvim
🦆 A NeoVim plugin for managing several debuggers for Nvim-dap (by Pocco81)
vscode-cpptools
Official repository for the Microsoft C/C++ extension for VS Code. (by microsoft)
| DAPInstall.nvim | vscode-cpptools | |
|---|---|---|
| 5 | 63 | |
| 233 | 5,359 | |
| - | 0.6% | |
| 8.8 | 9.3 | |
| over 2 years ago | 4 days ago | |
| Lua | TypeScript | |
| GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
DAPInstall.nvim
Posts with mentions or reviews of DAPInstall.nvim.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-02-02.
-
Debugging in NeoVim
To run your debugger, first, you need to install the needed debugger. To do this, run: :DIInstall followed by a tab. Go here to view the documentation on it.
-
Nvim-dap and go delve experience
In addition to the sibling comment, I used https://github.com/Pocco81/DAPInstall.nvim It provides some default configuration for a lot of debuggers.
-
Will we ever get nice debugging functionality in (neo)vim?
For a nice out of the box experience with nvim-dap you'd probably want to use DAPInstall.nvim.
-
DAPInstall.nvim: the plugin that makes installing and managing debuggers (with nvim-dap) accessible is now looking for maintainers!
I posted about DAPInstall.nvim a long time ago. If you don't know what it is, basically this plugin is like the :LspInstall but for debuggers. You can install with a simple command (:DIInstall ) and there is a default config for each one of the debuggers, which you can overwrite.
-
DAPInstall.nvim: a plugin for managing several debuggers for Nvim-dap (installation, setup, configuration, etc)
You could use, for instance, the python one as an example to write an installer for any of the debuggers supported by Nvim-dap.
vscode-cpptools
Posts with mentions or reviews of vscode-cpptools.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-05-04.
-
Xmake: A modern C/C++ build tool
Now if only MS would fix VSCode[0] :'(. Come on, the feature if more than half a decade old and this point.
0: https://github.com/microsoft/vscode-cpptools/issues/6302
-
🚀 Exciting New Feature Proposal for C++ Developers: "Add Similar Function" in IntelliSense! 🚀
🔗 Link to GitHub Issue: Add Similar Function - https://github.com/microsoft/vscode-cpptools/issues/11477
-
How to enable pretty printers?
According to this: https://github.com/microsoft/vscode-cpptools/issues/3423 it seems to be at least somewhat possible to reuse natvis files from Visual Studio, but I have not tested that. Never really had the need to look at any non-vector container in the debugger.
-
How to Debug C/C++ with Visual Studio Code (From a Microsoft Software Engineer)
Thank you for the feedback! Perf is always an ongoing issue for us but I can say that we’ve recently allocated one of our senior engineers to take on more perf related issues. Something that really helps us out is if you could file reproducible steps that lead to your performance issue. This allows us to address the issues more readily. Please file your issues here: https://github.com/microsoft/vscode-cpptools/issues
-
How to Setup VSCode for C/C++ Programming (From a Microsoft Software Engineer)
Yes, see this github issue for an example: Add Ada to supported languages for debugging · Issue #10475 · microsoft/vscode-cpptools (github.com)
-
Me after trying to use Git with Eclipse
Nope https://github.com/microsoft/vscode-cpptools/issues/16
- [Vscodium] L'extension C / C ++?
- εχει τρεξει κανεις cuda σε visual studio code ;
-
I can't properly use "Run C/C++ file"
and finally, it you're not happy using the extension I provided you, try fo contact the C/C++ Extension repo on GitHub, they'll help you out with your issue. Here's the link: https://github.com/microsoft/vscode-cpptools
-
[Vscode] VSCode me donnant une erreur lorsque j’utilise le débogueur : "launch: program enter name n’existe pas"
Vous devez définir le nom de votre exécutable dans launch.json. Ils expliquent ce qu'il faut faire et comment ici : https://github.com/Microsoft/vscode-cpptools/blob/master/launch.md
What are some alternatives?
When comparing DAPInstall.nvim and vscode-cpptools you can also consider the following projects:
nvim-dap-ui - A UI for nvim-dap
CodeLLDB - A native debugger extension for VSCode based on LLDB
nvim-dap - Debug Adapter Protocol client implementation for Neovim
vscode-clangd - Visual Studio Code extension for clangd
nvim-dap-go - An extension for nvim-dap providing configurations for launching go debugger (delve) and debugging individual tests
vscodium - binary releases of VS Code without MS branding/telemetry/licensing
DeathVim - A quick neovim setup.
vscode-lldb - A native debugger extension for VSCode based on LLDB [Moved to: https://github.com/vadimcn/codelldb]
vim-ultest - The ultimate testing plugin for (Neo)Vim
vimspector - vimspector - A multi-language debugging system for Vim
Bear - Bear is a tool that generates a compilation database for clang tooling.
DAPInstall.nvim vs nvim-dap-ui
vscode-cpptools vs CodeLLDB
DAPInstall.nvim vs nvim-dap
vscode-cpptools vs vscode-clangd
DAPInstall.nvim vs nvim-dap-go
vscode-cpptools vs vscodium
DAPInstall.nvim vs DeathVim
vscode-cpptools vs vscode-lldb
DAPInstall.nvim vs vim-ultest
vscode-cpptools vs nvim-dap
DAPInstall.nvim vs vimspector
vscode-cpptools vs Bear