From: Pedro Alves <palves@redhat.com>
To: Gary Benson <gbenson@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Implement completion limiting
Date: Wed, 12 Feb 2014 21:41:00 -0000 [thread overview]
Message-ID: <52FBEA9E.3060109@redhat.com> (raw)
In-Reply-To: <819294975.3055298.1392238425291.JavaMail.zimbra@redhat.com>
On 02/12/2014 08:53 PM, Gary Benson wrote:
> Pedro Alves wrote:
>> On 02/12/2014 11:57 AM, Gary Benson wrote:
>>> +@smallexample
>>> +(@value{GDBP}) b @key{TAB}@key{TAB}
>>> +Too many possibilities.
>>> +@end smallexample
>>> +
>>
>> Does the user lose the edit line after that, or can he
>> continue typing the command?
>
> You can continue typing, nothing is lost.
Like this?
@smallexample
(@value{GDBP}) b @key{TAB}@key{TAB}
Too many possibilities.
+ (@value{GDBP}) b
@end smallexample
Could you add that extra line to the example to make
that obvious in the docs?
>> I'd also suggest saying "completion candidates" instead of
>> "possibilities". Sounds more accurate / less vague to me.
>> (here and elsewhere in the docs and inline help as well)
>
> The reason I chose that as the message is to match up with
> readline's own messages:
>
> $ ls
> Display all 140 possibilities? (y or n)
>
> I'd prefer to keep "Too many possibilities" for consistency
Thanks, I agree, makes sense.
--
Pedro Alves
prev parent reply other threads:[~2014-02-12 21:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 11:55 [PATCH 0/2] Limit tab-completion result when list is large Gary Benson
2014-02-12 11:56 ` [PATCH 1/2] Add expansion_notify callback to expand_symtabs_matching Gary Benson
2014-02-12 20:10 ` Tom Tromey
2014-02-12 11:58 ` [PATCH 2/2] Implement completion limiting Gary Benson
2014-02-12 16:27 ` Eli Zaretskii
2014-02-12 16:41 ` Pedro Alves
2014-02-12 20:53 ` Gary Benson
2014-02-12 21:41 ` Pedro Alves [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=52FBEA9E.3060109@redhat.com \
--to=palves@redhat.com \
--cc=gbenson@redhat.com \
--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