From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 28714@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#28714: Shouldn't minibuffer-complete add a space after sole completions?
Date: Wed, 01 Dec 2021 04:42:34 +0800 [thread overview]
Message-ID: <87ee6xnznp.5.fsf@jidanni.org> (raw)
In-Reply-To: <87a815jzw0.fsf@jidanni.org>
>>>>> "LI" == Lars Ingebrigtsen <larsi@gnus.org> writes:
LI> 積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:
>> $ touch /tmp/abbbbb /tmp/abbbbbbbbbbbbbb
>> Find file or URL:
>> / [self-insert-command]
>> t [self-insert-command]
>> m [self-insert-command]
>> p [self-insert-command]
>> / [self-insert-command]
>> a [self-insert-command]
>> b [self-insert-command]
>> <tab> [minibuffer-complete]
>> <tab> [minibuffer-complete]
>> b b [self-insert-command]
>> <tab> [minibuffer-complete]
>> <tab> [minibuffer-complete]
>>
>> Now try the same thing in bash outside of emacs.
LI> So you basically want it to say "Sole completion" (or something) after
LI> the next-to-last TAB? I guess that would make sense (as an option), and
LI> is basically the same thing that's requested in bug#51650 (but there
LI> it's about things that do have several completions).
Yeah. Currently it takes two tabs for it to finally cough up "Sole
completion". What sense is that? It should do that with just one tab.
next prev parent reply other threads:[~2021-11-30 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 16:57 bug#28714: Shouldn't minibuffer-complete add a space after sole completions? 積丹尼 Dan Jacobson
2017-10-06 11:53 ` Stefan Monnier
2017-10-06 21:54 ` 積丹尼 Dan Jacobson
2017-10-07 7:28 ` Eli Zaretskii
2017-10-07 15:11 ` Stefan Monnier
2021-11-30 15:02 ` Lars Ingebrigtsen
2021-11-30 20:42 ` 積丹尼 Dan Jacobson [this message]
2017-10-08 0:49 ` 積丹尼 Dan Jacobson
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ee6xnznp.5.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=28714@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).