From: Nick Roberts <nickrob@snap.net.nz>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sources.redhat.com
Subject: Re: CLI commands in MI
Date: Thu, 11 May 2006 12:46:00 -0000 [thread overview]
Message-ID: <17507.7295.89096.763789@farnswood.snap.net.nz> (raw)
In-Reply-To: <20060511063929.GE27212@adacore.com>
> > Now, if we look at the command set someday (around mi4 maybe), and find
> > that it's become complete, then perhaps we can disable the CLI hack.
>
> How about if the front-end wants to provide a debugger console, so
> that the user can also enter commands manually? I would have hoped
> that we could still allow the user to use CLI commands in that console,
> because MI commands output are somewhat difficult to read for a normal
> human.
Thats what "-interpreter-exec console" is for. Bob is suggesting removing the
option of sending CLI commands directly to MI (which actually works pretty much
the same way now).
> Basically, the front-end would take the user command in CLI format,
> send it to the MI interpreter via this feature, and then get the
> output back, extract it from the MI output, and then display it
> on the console.
>
> Is there another way of doing this?
It switches the interpreter, executes the command, then switches back.
Don't ask me for the details though!
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-05-11 11:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 3:39 Bob Rossi
2006-05-11 6:08 ` Daniel Jacobowitz
2006-05-11 10:24 ` Joel Brobecker
2006-05-11 12:46 ` Nick Roberts [this message]
2006-05-11 10:40 ` Bob Rossi
2006-05-11 10:57 ` Nick Roberts
2006-05-11 11:24 ` Bob Rossi
2006-05-11 19:31 ` Eli Zaretskii
2006-05-11 20:57 ` Bob Rossi
2006-05-11 6:39 ` Nick Roberts
2006-05-11 10:46 ` Bob Rossi
2006-05-11 10:48 ` Nick Roberts
2006-05-11 10:54 ` Bob Rossi
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=17507.7295.89096.763789@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=brobecker@adacore.com \
--cc=gdb@sources.redhat.com \
/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