Live data from Hacker News

Debugging In Vim

zschoche.org

1–10 of 17 posts

Re: Debugging In Vim

#2
The site appears to be down for now but i got to the content via fullhn.com (there doesn't appear to be a permalink i can list for there, it's currently fullhn.com/#article-5)

Re: Debugging In Vim

#4
post #3

I don't get why you'd want a debugger in Vim when you could just use tmux to get what you want in a cleaner way.

One feature I can think of jumping to line numbers which come from make or compiler errors.

Re: Debugging In Vim

#5
post #4
post #3

I don't get why you'd want a debugger in Vim when you could just use tmux to get what you want in a cleaner way.

One feature I can think of jumping to line numbers which come from make or compiler errors.

Vim has that with its quickfix window.

Re: Debugging In Vim

#7
I highly recommend vdebug (https://github.com/joonty/vdebug) if you're looking for a great Vim interface to DBGP debuggers (for PHP, Python, Ruby, Perl, Node, etc.). Really nice, especially compared to the countless half-broken and out-of-date Vim/DBGP plugins that are scattered around vim.org and github.

Re: Debugging In Vim

#8
post #3

I don't get why you'd want a debugger in Vim when you could just use tmux to get what you want in a cleaner way.

I'd like to single-step through the code displayed in a vim editor window, with all the power of vim to navigate it, plus commands to single-step, watch variables, set breakpoints, etc. tmux or screen can't give me that, nor can gdb -tui.

Re: Debugging In Vim

#9
post #7

I highly recommend vdebug ( https://github.com/joonty/vdebug ) if you're looking for a great Vim interface to DBGP debuggers (for PHP, Python, Ruby, Perl, Node, etc.). Really nice, especially compared to the countless half-broken and out-of-date Vim/DBGP plugins that are scattered around vim.org and github.

Maybe this is great for PHP, where DBGP is the standard, but...

I tried this for Python and was greatly put off by the need to download an obscure debugger tarball from ActiveState with some weird license on it, then (according to the vdebug documentation) run a very long command line by hand passing the name of the script every time I want to debug something.

If I am going to trouble myself with that, it's hard to understand why I don't just run a standard standalone debugger which works in the expected way, from the command line. I definitely don't see how it reproduces the experience of (say) pressing a debug button in Visual Studio or Xcode.

Post reply on HN