From: Bob Rossi <bob_rossi@cox.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb-patches@sources.redhat.com
Subject: Re: CLI and GDB/MI documentation patch
Date: Fri, 12 May 2006 13:56:00 -0000 [thread overview]
Message-ID: <20060512130031.GE26655@brasko.net> (raw)
In-Reply-To: <uu07v7a5j.fsf@gnu.org>
On Fri, May 12, 2006 at 02:30:32PM +0300, Eli Zaretskii wrote:
> > From: Vladimir Prus <ghost@cs.msu.su>
> > Date: Fri, 12 May 2006 12:13:24 +0400
> >
> > I'd agree with Eli that the proposed text sounds a bit like history, but it
> > documents some important points:
> >
> > - That you can type CLI commands into MI, and this is not longer considered
> > to work just by accident
> > - That typing CLI command has the same effect as -interpreter-exec console
> > - That CLI command don't produce async notifications
> >
> > Those points are important to have documented, IMO.
>
> I agree.
>
> Bob, are there any other points you wanted to make? If so, please
> tell what they are.
haha. I am the worst at writing documentation, but I try anyways!
I think it's important to mention that mi2 supports receiving CLI
commands directly into the interpreter, but only after a certain
point in it's development. Early on it wasn't supported, so the
only safe way of passing CLI commands directly is to use
-interpreter-exec.
> > - That you can type CLI commands into MI, and this is not longer considered
> > to work just by accident
This was never considered to be used be the FE before.
> > - That CLI command don't produce async notifications
I think it's important to mention that this will most likely change in
the future and that currently this is a lack of a feature.
Thanks,
Bob Rossi
next prev parent reply other threads:[~2006-05-12 12:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 1:16 Bob Rossi
2006-05-12 7:53 ` Eli Zaretskii
2006-05-12 8:14 ` Vladimir Prus
2006-05-12 11:30 ` Eli Zaretskii
2006-05-12 13:56 ` Bob Rossi [this message]
2006-05-12 12:49 ` Daniel Jacobowitz
2006-05-12 12:54 ` Daniel Jacobowitz
2006-05-12 13:58 ` Eli Zaretskii
2006-05-12 14:02 ` Daniel Jacobowitz
2006-05-12 14:10 ` Bob Rossi
2006-05-12 18:32 ` Eli Zaretskii
2006-05-12 18:37 ` Eli Zaretskii
2006-05-12 18:55 ` Daniel Jacobowitz
2006-05-12 19:01 ` Eli Zaretskii
2006-05-12 19:16 ` Daniel Jacobowitz
2006-05-12 19:51 ` Bob Rossi
2006-05-13 9:28 ` Eli Zaretskii
2006-05-15 15:50 ` Daniel Jacobowitz
2006-05-12 20:26 ` PAUL GILLIAM
2006-05-13 8:45 ` Eli Zaretskii
2006-05-12 12:59 ` Bob Rossi
2006-05-12 14:12 ` Eli Zaretskii
2006-05-12 14:30 ` Bob Rossi
2006-05-12 18:28 ` Eli Zaretskii
2006-05-12 19:19 ` Bob Rossi
2006-05-13 8:09 ` Eli Zaretskii
2006-05-13 11:02 ` Bob Rossi
2006-05-13 14:29 ` Eli Zaretskii
2006-05-29 19:05 ` Bob Rossi
2006-05-30 7:17 ` Eli Zaretskii
2006-05-12 12:44 Nick Roberts
2006-05-12 14:19 ` Eli Zaretskii
2006-05-12 16:42 ` Bob Rossi
2006-05-12 22:14 ` Nick Roberts
2006-05-12 22:19 ` Bob Rossi
2006-05-13 9:13 ` Nick Roberts
2006-05-13 16:04 ` Daniel Jacobowitz
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=20060512130031.GE26655@brasko.net \
--to=bob_rossi@cox.net \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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