From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] MI Doco
Date: Fri, 09 Jun 2006 19:57:00 -0000 [thread overview]
Message-ID: <20060609195743.GA7720@nevyn.them.org> (raw)
In-Reply-To: <u7j3qqf99.fsf@gnu.org>
On Fri, Jun 09, 2006 at 10:51:30PM +0300, Eli Zaretskii wrote:
> > Date: Fri, 9 Jun 2006 15:11:34 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: Nick Roberts <nickrob@snap.net.nz>, gdb-patches@sources.redhat.com
> >
> > On Fri, Jun 09, 2006 at 10:06:34PM +0300, Eli Zaretskii wrote:
> > > > + @smallexample
> > > > + -> -break-insert main
> > > > + <- ^done,bkpt=@{number="1",type="breakpoint",disp="keep",
> > > > + enabled="y",addr="0x08048564",func="main",file="myprog.c",
> > > > + fullname="/home/nickrob/myprog.c",line="68",times="0"@}
> > > > + <- (gdb)
> > >
> > > Please use "(@value{GDBP})" instead of a literal "(gdb)".
> >
> > In this context, that's incorrect. This is actually a literal
> > "(gdb)\n", rather than the result of "show prompt"; MI uses a hardcoded
> > prompt string.
>
> Are you saying that all the MI examples that use @value{GDBP} are
> incorrect?
Yes, I'm afraid so.
> Also, isn't it a bug in MI that it uses a hardcoded string?
Nope. The prompt is part of the formal grammar; the grammar changing
when the user used "set prompt" would be confusing to front ends. You
can have both the CLI and MI live at once, so you want to change the
CLI's prompt, but leave MI's alone.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-09 19:57 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 [this message]
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
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=20060609195743.GA7720@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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