gdb-dashboard VS asyncrun.vim

To debug, termdebug is built in to vim and supports a front end to gdb. In combination with gdb-dashboard this gives a reasonably good debugging experience

https://github.com/cyrus-and/gdb-dashboard, https://github.com/cyrus-and/gdb-dashboard/wiki

You can use the Python API to GDB to get really fancy TUIs like this: https://github.com/cyrus-and/gdb-dashboard

Try GDB Dashboard, it makes gdb much easier to use:

https://github.com/cyrus-and/gdb-dashboard

There's also Voltron which works with both gdb and lldb (amongst others):

https://github.com/snare/voltron

I can't believe no one has mentioned `gdb-dashboard` [1] yet! I use it extensively. [2]

Beyond that, I have recently learned how to write custom pretty printers for GDB. This saves a lot of screen space. I should probably update [2] soon with those new techniques.

GDB is powerful, useful, and after getting my start in IDE debuggers, including Visual Studio, I struggle whenever I have to go back.

[1]: https://github.com/cyrus-and/gdb-dashboard

[2]: https://gavinhoward.com/2020/12/my-development-environment-a...

Debugging: Learn gdb. You can use it for assembly. You can use it for C on a MCU. You can use it for Go on a Linux system. It’s ubiquitous, versatile, and worth understanding. You can pretty-print the output with something like this to help you out at first. There are 2 things you need, however: on chip debugger and a debug probe (though you don’t need an expensive one). Effectively, you talk to GDB, GDB talks to the server exposed by OCD, OCD knows the debug probe protocol, and the debug probe can use the MCU debug peripheral via SWD or JTAG to get those details.

I use gdb because I'm usually in the terminal. I don't think terminal it's any faster though. This is a nice addition to boring old terminal gdb.

asyncrun - 🚀 Run Async Shell Commands in Vim 8.0 and NVim and Output to the Quickfix Window !!

I'm familiar with asyncrun.vim, but it outputs as quickfix. I specifically want to filter editor text (as stdin/stdout).

If you want to open a new terminal in the CWD of neovim, you couls either use neovim's built in terminal or, if it needa to be kitty, use the neovim AsyncRun-plugin and start kitty with the necessary command-line options to start in neovims's CWD(I uae this with Alacritty instead of Kitty).

For running the file there are several tools. I have been using asynctasks.vim which is built on top of asyncrun.vim which I usually use to open a tmux pane and run the code/test. I've been looking at switching to overseer.nvim but haven't yet. I use justfiles to define all of my tasks.

I can :Man blah to look up docs or :AsyncRun to build/run with jumpable output in the quickfix. Doing it within vim means I can pull from any register for pasting, yank without a mouse, hide buffers or move them to tabs, etc.

I use asyncrun.vim to see compile output as it happens (line by line instead of the whole dump when compile completes) and asynchronously (so I can keep navigating around).

try asyncrun:

Also AsyncRun and AsyncTasks worth a mention.

Hey folks, I'm using asyncrun to run async commands on vim, but some of them output ansi colorcodes, I've found powerman's AnsiEsc which is able to conceal and highlight them very well, but that only work for the current buffer, so there's no way to automate it from g:asyncrun_exit and I can't set the -post from asynctasks, has anyone found a way to fix this?