From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: 17375@debbugs.gnu.org
Subject: bug#17375: 24.4.50; minibuffer completion by SPC
Date: Wed, 30 Apr 2014 21:53:30 -0400 [thread overview]
Message-ID: <jwvbnvip9zo.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <b4mtx9aic66.fsf@jpl.org> (Katsumi Yamaoka's message of "Thu, 01 May 2014 09:18:41 +0900")
> (get-buffer-create "foo-bar")
> That's all!
> Could you try this on `emacs -Q'? And you will see that the first
> SPC for `C-x b' doesn't insert a space (I'm not quite sure if it
> happens on every platform, though).
> Maybe a buffer-name containing a hyphen triggers this problem.
Indeed, that's it.
It's due to the fix for http://debbugs.gnu.org/15980.
I.e. if we have buffer names " toto" and "foo-bar", then both " " and
"-" have valid completions (remember: C-x b uses substring completion),
so bug#15980 says that instead of choosing arbitrarily between " " and
"-", we should just leave the input unchanged.
I must say I dislike "word completion". Both because its behavior is
largely ill-defined (e.g. what does it mean to "complete at most
a single word" when the completion table completes "a-b-$FOO-a" to
"a-b-c-a-d-a"?), and because I'd rather leave SPC as a self-insert key.
So in this case, I'd tend to prefer reverting the fix for bug#15980, so
that " " is preferred over "-" on the premise that it makes SPC behave
a bit more like self-insert-command.
Stefan
next prev parent reply other threads:[~2014-05-01 1:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 7:50 bug#17375: 24.4.50; minibuffer completion by SPC Katsumi Yamaoka
2014-04-30 12:44 ` Stefan Monnier
2014-04-30 13:30 ` Katsumi Yamaoka
2014-04-30 13:50 ` Katsumi Yamaoka
2014-04-30 18:07 ` Stefan Monnier
2014-05-01 0:18 ` Katsumi Yamaoka
2014-05-01 1:53 ` Stefan Monnier [this message]
2014-05-06 12:48 ` Stefan Monnier
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=jwvbnvip9zo.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=17375@debbugs.gnu.org \
--cc=yamaoka@jpl.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.