Hi Xavier,
I notice that the functionality of CTRL-p in pyclewn is different than with
vimgdb, and perhaps is broken when using pyclewn with vim on a console? When I
press CTRL-p, it just sends a "print" command to gdb, which answers:
The history is empty.
or the previously printed variable. When I issue :Cprint my_var, it works
fine.
Am I doing something wrong or does this have to do with the differences in
gvim and vim?
Olaf
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Pyclewn-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pyclewn-general
