News for hackers. Stuff that matters.
Re:Debugging In Vim by DiabloD3 on Monday September 30, 2013 @12:37PM (#6470545)
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.
Re:Debugging In Vim by JoshTriplett on Monday September 30, 2013 @02:18PM (#6471257)
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 by jmcdowell on Monday September 30, 2013 @03:53PM (#6471913)
I was looking for the same thing, ended up using ddd, has watches, breakpoints etc. If you've found a better solution than that though feel free to let me know.
Re:Debugging In Vim by JoshTriplett on Monday September 30, 2013 @04:07PM (#6472016)
For everything except the data structure graphs, I prefer gdb's -tui option (split-screen code and "(gdb)" prompt) over ddd.
Re:Debugging In Vim by tareqak on Monday September 30, 2013 @12:43PM (#6470609)
One feature I can think of jumping to line numbers which come from make or compiler errors.
Re:Debugging In Vim by chongli on Monday September 30, 2013 @12:50PM (#6470652)
Vim has that with its quickfix window.
Re:Debugging In Vim by dllthomas on Monday September 30, 2013 @04:35PM (#6472183)
For live debugging there's still a need for some way of getting the source locations you're interested in into that quickfix window. Not that there aren't probably plugins &c that do just that, but it doesn't fall out as straightforwardly as parsing build errors.