On Wed, Dec 7, 2011 at 12:38 PM, Rob wrote: >>This is because some CLI commands, such as `if', `when' and `define', >>are not valid with gdb/MI, and pyclewn uses gdb/MI to run the gdb >>commands. > > Could it be done with -interpreter-exec? Is the problem providing > the subsequent user input?
It cannot be done with -interpreter-exec, the above commands are excluded from the set of commands that run with -interpreter-exec. >>But it is much more convenient (IMHO) to write the 'define' and >>'command' sequences in a Vim temporary buffer and source the >>corresponding file with the gdb 'source' command. > > Yes, this is a good work-around but I would still prefer to do it > directly (possibly pyclewn could do this behind the scenes?). I > will just be defining temporary sequences and this requires more > typing. I will try to write a Vim script that does that. -- Xavier Les Chemins de Lokoti: http://lokoti.alwaysdata.net ------------------------------------------------------------------------------ Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ _______________________________________________ Pyclewn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyclewn-general
