From: Matt Rice <ratmice@gmail.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [patch/rfc] mi interpreter-complete enh req 8058.
Date: Mon, 05 Oct 2009 08:00:00 -0000 [thread overview]
Message-ID: <8ba6bed40910050100y241537a5od4346aafd5168c9f@mail.gmail.com> (raw)
In-Reply-To: <19143.59472.547182.54020@totara.tehura.co.nz>
On Sat, Oct 3, 2009 at 5:12 PM, Nick Roberts <nickrob@snap.net.nz> wrote:
> > Thanks, I had missed this CLI command somehow, it will work for now,
> > ideally i would like it not to be going directly to stdout like that
> > output infers, I guess i could change the output filehandle, when
> > executing this command until it finishes,
>
> I'm not sure what you mean. Everything goes to stdout but you can
> eliminate the LOG-STREAM-OUTPUT (prefixed by `&') by using
> -interpreter-exec:
>
> (gdb)
> -interpreter-exec console "complete b ma"
> ~"b main\n"
> ~"b malloc\n"
> ~"b malloc@plt\n"
> ^done
> (gdb)
>
I meant the ~"b main\n" etc,
"~" string-output
The console output stream contains text that should be displayed
in the CLI console window. It contains the textual responses to CLI
commands.
I would like this output not to go to the CLI console window, but to a
new window or a new tab, which switches back to the console window
upon hitting 'enter', but is also a list control,allowing you to
select the tab completion result with the mouse or entering it by
hand, using the complete CLI command means monkeying around at the MI
parser level, parsing the string output based on the command executed.
anyhow, complete CLI command will suffice for now.
> > so that the output history
> > isn't filled with this temporal information which always bothers me...
>
> You can use the server prefix to suppress commands being entered into
> the command history.
ahh, sorry i didn't mean that history, I meant the 'CLI console output
stream', but noted.
> > additionally its worth noting the patch screws this output up.
>
> Does that not show up in the testsuite?
no, it looks like additional unwanted output when executing the
complete command, the output being tested for is still there so the
tests still pass i gather.
> What front end are you working on?
one which doesn't really have any tangible existence I just saw this
on the bugzilla, and taking a break from other patches...
initially trying to do a faithful reproduction of the CLI, then then
augmenting it with some gui stuff, but mainly keeping the console
roots, no built in editor or fancy stuff.
prev parent reply other threads:[~2009-10-05 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 17:37 Matt Rice
2009-10-02 20:55 ` Tom Tromey
2009-10-02 23:10 ` Nick Roberts
2009-10-03 19:00 ` Matt Rice
2009-10-04 0:12 ` Nick Roberts
2009-10-05 8:00 ` Matt Rice [this message]
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=8ba6bed40910050100y241537a5od4346aafd5168c9f@mail.gmail.com \
--to=ratmice@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=nickrob@snap.net.nz \
--cc=tromey@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