You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great work in integrating GDB in this awesome editor.
I wonder if with your integration you might have the possibility to create a view to enable gdb console commands, just like vimgdb does it. Seems old fashioned but very powerful.
I am considering to invest some time to code this integration if you evaluate it as a useful feature.
I am considering to move to atom, if I can perform everything I do in VIM. :-)
Integration with GDB is a key element.
Best regards
The text was updated successfully, but these errors were encountered:
This GDB feature, that is made for that: (new in 7.12)
Support for running interpreters on specified input/output devices
GDB now supports a new mechanism that allows frontends to provide
fully featured GDB console views, as a better alternative to
building such views on top of the "-interpreter-exec console"
command. See the new "new-ui" command below. With that command,
frontends can now start GDB in the traditional command-line mode
running in an embedded terminal emulator widget, and create a
separate MI interpreter running on a specified i/o device. In this
way, GDB handles line editing, history, tab completion, etc. in the
console all by itself, and the GUI uses the separate MI interpreter
for its own control and synchronization, invisible to the command
line.
Great work in integrating GDB in this awesome editor.
I wonder if with your integration you might have the possibility to create a view to enable gdb console commands, just like vimgdb does it. Seems old fashioned but very powerful.
I am considering to invest some time to code this integration if you evaluate it as a useful feature.
I am considering to move to atom, if I can perform everything I do in VIM. :-)
Integration with GDB is a key element.
Best regards
The text was updated successfully, but these errors were encountered: