nvim-gdb VS vimspector

It's not ideal to me yet. I've had some problems with DAP. The DAP servers I've checked were a bit unstable and slow. For now I'm using gdb with nvim-gdb https://github.com/sakhnik/nvim-gdb

Very reliable and as fast as gdb is. But with all the problems just using gdb has.

Maybe https://github.com/sakhnik/nvim-gdb (bashdb uses gdb like commands) I've mostly used llvm debugger and node debugger so I am not too familiar with gdb.

nvim-gdb: GDB wrapper, simple and easy to hack.

Recently I am using nvim-gdb, which is inspired by neovim-gdb.vim script. I am wondering whether it is possible to have the same visual interface in terms of current line running as well as the breakpoint mark similar to the above two project but not connect to the debug?

There's the plugin that evolved from the original neovim debugger: sakhnik/nvim-gdb. Well tested and maintained. Spoiler: personal affiliation.

sakhnik/nvim-gdb This one also looks like a nice debugger plugin; also neovim only.

https://www.dannyadam.com/blog/2019/05/debugging-in-vim/ describes it well. https://github.com/sakhnik/nvim-gdb is nicer, but requires neovim.

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.