From: nickrob@snap.net.nz (Nick Roberts)
To: tromey@redhat.com
Cc: Matt Rice <ratmice@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [patch/rfc] mi interpreter-complete enh req 8058.
Date: Fri, 02 Oct 2009 23:10:00 -0000 [thread overview]
Message-ID: <19142.34895.136190.624637@totara.tehura.co.nz> (raw)
In-Reply-To: <m3r5tlo6s1.fsf@fleche.redhat.com>
Tom Tromey writes:
> >>>>> "Matt" == Matt Rice <ratmice@gmail.com> writes:
>
> Matt> Attached is a patch i've ported from Apple's gdb...
> Matt> it implements a tab-completion like function for MI
> Matt> http://sourceware.org/bugzilla/show_bug.cgi?id=8058
> Matt> I figured I would post a basic port of the patch for discussion,
> Matt> before doing to much to it.
>
> Thanks.
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.
> ...
> Matt> -interpreter-complete console "b ma"
> Matt> ^done,completions=[c="main",c="malloc",c="malloc@plt"]
>
> It is weird to see all those useless "c=" strings in there :-)
Well, if they are going to be present, could we please stick to the syntax
suggested in the manual:
`TUPLE ==>'
` "{}" | "{" RESULT ( "," RESULT )* "}" '
and
* New GDB/MI commands should only output LISTS containing VALUES.
So either
^done,completions={c="main",c="malloc",c="malloc@plt"}
or
^done,completions=["main","malloc","malloc@plt"]
--
Nick http://users.snap.net.nz/~nickrob
next prev parent reply other threads:[~2009-10-02 23:10 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 [this message]
2009-10-03 19:00 ` Matt Rice
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=19142.34895.136190.624637@totara.tehura.co.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@sourceware.org \
--cc=ratmice@gmail.com \
--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