DAPInstall.nvim
vimspector
DAPInstall.nvim | vimspector | |
---|---|---|
5 | 100 | |
233 | 4,023 | |
- | - | |
8.8 | 8.0 | |
over 2 years ago | 8 days ago | |
Lua | Vim Script | |
GNU General Public License v3.0 only | Apache License 2.0 |
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
-
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.
vimspector
-
I can't stand using VSCode so I wrote my own (it wasn't easy)
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.
- Shape Typing in Python
-
Certain Mapping only when another command was called earlier (lua)
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).
-
Vimspector – the Vim debugger rules all
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...
-
How to configure vim like an IDE
vimspector
-
I like Tabasco.
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.
-
Rust, RR, Neovim: A perfect debug combination
You could try vimspector. It's main target is vim and not neovim.
https://github.com/puremourning/vimspector/
-
Vim or Emacs for C++ Coding?
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
-
My office wants everyone to use vim as the only editor. Has this happened to anyone else?
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.
What are some alternatives?
nvim-dap-ui - A UI for nvim-dap
nvim-dap - Debug Adapter Protocol client implementation for Neovim
nvim-gdb - Neovim thin wrapper for GDB, LLDB, PDB/PDB++ and BashDB
nvim-dap-go - An extension for nvim-dap providing configurations for launching go debugger (delve) and debugging individual tests
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.
DeathVim - A quick neovim setup.
vim-plug - :hibiscus: Minimalist Vim Plugin Manager
vim-ultest - The ultimate testing plugin for (Neo)Vim
ipdb - Integration of IPython pdb
vscode-cpptools - Official repository for the Microsoft C/C++ extension for VS Code.
omnisharp-roslyn - OmniSharp server (HTTP, STDIO) based on Roslyn workspaces