This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC/doc] Interpreters documentation


On Fri, 30 Aug 2002, Eli Zaretskii wrote:

Sorry for the long delay, I misread this message...

> > > Is interpreter-exec documented elsewhere in the manual (I cannot find it 
> > > in my sandbox, but maybe I'm not up-to-date)?  If not, you should add a 
> > > @kindex entry here (we have a @kindex for every GDB command).
> > 
> > interpreter-exec is a new command. It is mentioned in the gdbmi.texinfo 
> > file on the interpreter branch (which I have not yet submitted).
> 
> Then please add a @pxref to the section in gdbmi.texinfo where this
> command is documented in full.

interpreter-exec is both an mi command and a console command. The 
interpreter chapter in the gdb manual (gdb.texinfo proper, that is), 
defines this command. I've added a @kindex for it where it is described. I 
can add a cross-reference to the equivalent MI command when I commit the 
MI changes (yes, this command is documented in gdbmi.texinfo, but only on 
the branch).

Here's what I've done, which admittedly is the path of least resistance 
(aka typing ;-).  Please make recommendation if you'd like to see 
something different.

Keith

[snip]
+ @kindex interpreter-exec
+ Although you may only choose a single interpreter at startup, you may execute
+ commands in any interpreter from the current interpreter using the appropriate
+ command.  If you are running the console interpreter, simply use the
+ @code{interpreter-exec} command:
[snip]



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]