Subject: bug#28714: Shouldn't minibuffer-complete add a space after sole completions?

From: 積丹尼 Dan Jacobson <[email-masked]>
Date: Sat, 07 Oct 2017 05:54:44 +0800

$ 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.

The user at every moment is aware how many completions there are, and it
only takes a total of two tabs vs. four in emacs.

>>>>> "SM" == Stefan Monnier <[email-masked]> writes:

SM> Depends in which context: for example when completing for `M-x` or `C-x
SM> C-f`, adding a space at the end would be an error since with the space
SM> it would not correspond to an existing command or file name any more.

How about perhaps just adding the space for the user's visual pleasure,
but not using it when processing the command / filename?

Another idea might be not requiring a second TAB before telling the user
[Sole completion] etc. but that would seem too chatty.

Anyway if he really wants a space he could use "\ ".