vimspector VS pudb

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.

I simply use the superb pudb. Press ctrl+e to open the current file at the current line in your editor.

such a waste of time...

To this day, I'm baffled by the dynamic language folks who cannot get they head around how strictness/rigor (via a good expressive type system) actually makes maintenance easier and more importantly: cheaper.

[1] https://github.com/inducer/pudb

I use the very under-rated pudb in an adjacent terminal window.

I've been using PuDB for a while now.

I think it is also worth mentioning pudb here

Most of the time I simply use icecream (a much better version of print()), and sometimes, I use pudb (a visual debugger) for tougher/trickier bugs.

For a quick view etc I usually fire up pudb in an adjacent terminal window but for a detailed/heavy debugging session I fire up VS Code (with the vim plugin of course). I have used vi/vim for 37+ years now so it is part of my DNA and use VS Code only for it's great vim + debugging facility.

Two that I haven’t seen here and have saved me tons of time are pudb, a great debugger and petl a simple powerful ETL toolkit.

If you want to debug Python then pudb is simply superb. Vim users don't really want or need to "debug inside of vim" do they? We usually are happy to use multiple command line and other tools in adjacent windows. Also, you can just step around and view variables etc in pudb and then press ctrl+e to edit that file in vim, then q to restart debugger.