From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] MI Doco
Date: Sat, 10 Jun 2006 07:51:00 -0000 [thread overview]
Message-ID: <uzmglphxl.fsf@gnu.org> (raw)
In-Reply-To: <17546.915.125070.943811@kahikatea.snap.net.nz> (message from Nick Roberts on Sat, 10 Jun 2006 11:26:11 +1200)
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Sat, 10 Jun 2006 11:26:11 +1200
> Cc: gdb-patches@sources.redhat.com
>
> > > ! However, CLI commands that use sequences of commands such @code{source},
> > > ! @code{commands} will not work
> >
> > I don't understand from this text what will not work. (Please enclose
> > input that would be typed by user in @kbd, btw.) Do you mean if I
> > type "source, commands", it will not work? Or do you mean something
> > else?
> >
> > Also, you are missing "as" after "such", I think.
>
> I'm not sure what I meant either. I committed this part, as is, inadvertantly
> but I've tried to address it as part of the patch below. Sorry.
Maybe you meant `commands', `while', etc.--those commands that prompt
for the body which ends with `end'? Then `source' is not part of the
endangered commands.
> > > ! target. This is only present when GDB's event loop
> >
> > Please use @value{GDBN} instead a literal "GDB".
>
> I left this unchanged after reading the ensuing discussion.
The discussion was about "(gdb)" vs "(@value{GDBP})". "GDB" should
still be converted to "@value{GDBN}", as that has nothing to do with
"set prompt".
But I see you did remove literal "GDB".
> just note that all I did here was move existing text.
Yes, I know. Thanks.
> In the patch below, I'm trying to group the commands in a similar (but not
> identical) fashion to the CLI commands in the main part of the manual. To
> that end, I would like to have the node ordering:
>
> * GDB/MI Breakpoint Commands::
> * GDB/MI Program Context::
> * GDB/MI Thread Commands::
> * GDB/MI Program Execution::
> * GDB/MI Stack Manipulation::
> * GDB/MI Variable Objects::
> * GDB/MI Data Manipulation::
> * GDB/MI Tracepoint Commands::
> * GDB/MI Symbol Query::
> * GDB/MI File Commands::
> * GDB/MI Target Manipulation::
> * GDB/MI Miscellaneous Commands::
>
> I've not done this in the patch because it would make it totally unreadable,
> of course. Is such an ordering acceptable?
Yes.
next prev parent reply other threads:[~2006-06-10 7:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 0:23 Nick Roberts
2006-06-02 9:05 ` Eli Zaretskii
2006-06-02 10:23 ` Nick Roberts
2006-06-02 10:44 ` Eli Zaretskii
2006-06-03 23:57 ` Nick Roberts
2006-06-04 19:32 ` Eli Zaretskii
2006-06-09 19:07 ` Eli Zaretskii
2006-06-09 19:12 ` Daniel Jacobowitz
2006-06-09 19:52 ` Eli Zaretskii
2006-06-09 19:57 ` Daniel Jacobowitz
2006-06-10 7:32 ` Eli Zaretskii
2006-07-01 12:35 ` [commit] Fix MI prompt in manual (was: MI Doco) Eli Zaretskii
2006-06-09 19:58 ` [PATCH] MI Doco Bob Rossi
2006-06-09 23:27 ` Nick Roberts
2006-06-10 7:51 ` Eli Zaretskii [this message]
2006-06-10 21:40 ` Nick Roberts
2006-06-11 3:31 ` Eli Zaretskii
2006-06-11 10:47 ` Nick Roberts
2006-06-11 19:27 ` Eli Zaretskii
2006-06-11 21:42 ` Nick Roberts
2006-06-12 3:36 ` Eli Zaretskii
2006-06-12 6:19 ` Nick Roberts
2006-06-13 3:39 ` Eli Zaretskii
2006-06-13 4:46 ` Nick Roberts
2006-06-13 17:26 ` Eli Zaretskii
2006-06-13 21:15 ` Nick Roberts
2006-06-14 18:30 ` Eli Zaretskii
2006-06-14 21:05 ` Nick Roberts
2006-06-15 6:56 ` Eli Zaretskii
2006-06-30 2:13 ` Nick Roberts
2006-06-30 12:09 ` Eli Zaretskii
2006-06-30 14:12 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uzmglphxl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox