From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Completion of add-inferior
Date: Fri, 11 May 2012 20:58:00 -0000 [thread overview]
Message-ID: <87fwb6xwny.fsf@fleche.redhat.com> (raw)
In-Reply-To: <83obpuxwr4.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 11 May 2012 23:56:15 +0300")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Eli> In what way is it not ideal? Did you want to complete on file names
Eli> only when -exec was used? I thought about that, but then I realized
Eli> that any other way of invoking that command cannot benefit from any
Eli> completion at all.
Eli> Or did you have something else in mind?
Yeah, it could be context-sensitive; and also complete the options as
well.
I don't think it is very important.
In my mind I immediately went to having a gdb-specific getopt that also
had completion callbacks; funny overkill of the sort programmers are
susceptible to :)
Tom
next prev parent reply other threads:[~2012-05-11 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 17:51 Eli Zaretskii
2012-05-11 20:21 ` Tom Tromey
2012-05-11 20:55 ` Eli Zaretskii
2012-05-11 20:58 ` Tom Tromey [this message]
2012-05-12 6:36 ` Eli Zaretskii
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=87fwb6xwny.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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