all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 34622@debbugs.gnu.org
Subject: bug#34622: Find file prompt should indicate sole completion by appending a blank
Date: Sat, 23 Feb 2019 09:36:16 +0200	[thread overview]
Message-ID: <83bm33q7m7.fsf@gnu.org> (raw)
In-Reply-To: <87k1hrijt4.fsf@jidanni.org>

tags 34622 notabug
thanks

> From: 積丹尼 Dan Jacobson
> 	<jidanni@jidanni.org>
> Date: Sat, 23 Feb 2019 05:40:07 +0800
> 
> With emacs, one can never be sure if the expansion
> Find file or URL: ~/bin/wwzz
> is the sole completion or not, without needing a second TAB press to get
> "[Sole completion]" shown.

Which command did that?  "C-x C-f" shows just the directory, so
there's no question of completions with the initial prompt.  The
situation you describe is thus not entirely clear.

But in general, this default behavior is on purpose (there are add-on
packages which give you immediate feedback about candidates).
File-name completion is special, by design.

> With bash, there is always a space added at end,
> "$ wc ~/bin/wwzz "
> so we know right away.

Bash is not an editor, so the considerations are different.  For
example, Bash doesn't need to consider the possibility that the user
would like to create a new file.

> I propose that emacs do the same:
> "Find file or URL: ~/bin/wwzz "
> and if they really want to enter a file with a " " at the end, well they
> could use C-q (quoted-insert).

Asking users to use C-q for whitespace embedded in a file name is a
non-starter.  We did the opposite change several Emacs versions ago.





  reply	other threads:[~2019-02-23  7:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22 21:40 bug#34622: Find file prompt should indicate sole completion by appending a blank 積丹尼 Dan Jacobson
2019-02-23  7:36 ` Eli Zaretskii [this message]
2019-02-24  4:36   ` 積丹尼 Dan Jacobson
2019-02-24 16:05     ` Eli Zaretskii
2019-02-27  5:20       ` 積丹尼 Dan Jacobson
2019-02-27 15:50         ` Eli Zaretskii
2019-09-16  3:13 ` Stefan Kangas

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=83bm33q7m7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34622@debbugs.gnu.org \
    --cc=jidanni@jidanni.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.