unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 28714@debbugs.gnu.org
Subject: bug#28714: Shouldn't minibuffer-complete add a space after sole completions?
Date: Sat, 07 Oct 2017 05:54:44 +0800	[thread overview]
Message-ID: <87y3ooymaj.fsf@jidanni.org> (raw)
In-Reply-To: <87a815jzw0.fsf@jidanni.org>

$ 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 <monnier@iro.umontreal.ca> 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 "\ ".





  parent reply	other threads:[~2017-10-06 21:54 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 [this message]
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
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=87y3ooymaj.fsf@jidanni.org \
    --to=jidanni@jidanni.org \
    --cc=28714@debbugs.gnu.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).