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: Sat, 03 Oct 2009 19:00:00 -0000 [thread overview]
Message-ID: <8ba6bed40910031159v6508a55ap4fd02b253c599794@mail.gmail.com> (raw)
In-Reply-To: <19142.34895.136190.624637@totara.tehura.co.nz>
On Fri, Oct 2, 2009 at 4:10 PM, Nick Roberts <nickrob@snap.net.nz> wrote:
<snip>
> PR 8058 goes back to 2003. I don't see the need for MI to duplicate all of
> the CLI functionality. Emacs just uses the CLI command "complete" which is
> clearly just intended for front end use:
>
> complete b ma
> &"complete b ma\n"
> ~"b main\n"
> ~"b malloc\n"
> ~"b malloc@plt\n"
> ^done
>
> The lisp function, gud-gdb-complete-command. is bound to TAB to it works
> in the GUD buffer (Emacs' console) just as it does on the command line.
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, so that the output history
isn't filled with this temporal information which always bothers me...
additionally its worth noting the patch screws this output up.
next prev parent reply other threads:[~2009-10-03 19: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 [this message]
2009-10-04 0:12 ` Nick Roberts
2009-10-05 8:00 ` Matt Rice
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=8ba6bed40910031159v6508a55ap4fd02b253c599794@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