From: Bastien Guerry <bzg@altern.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 15980@debbugs.gnu.org
Subject: bug#15980: 24.3.50; `minibuffer-complete-word': case where it does not work correctly
Date: Tue, 07 Jan 2014 13:04:55 +0100 [thread overview]
Message-ID: <87d2k4hu77.fsf@bzg.ath.cx> (raw)
In-Reply-To: <20db5440-5f90-46d1-b0a2-25f495661ae6@default> (Drew Adams's message of "Tue, 26 Nov 2013 09:11:45 -0800 (PST)")
Drew Adams <drew.adams@oracle.com> writes:
> Seems like the behavior is wrong in this case, but I see that the same
> behavior is found for Emacs 20 through 24. So I cannot say for sure
> whether this is a bug. At least the behavior does not seem to follow
> the doc.
>
> The doc ((emacs) `Completion Commands') says that SPC does this:
>
> Complete up to one word from the minibuffer text before point
> (`minibuffer-complete-word').
>
> emacs -Q
>
> (defun cmd\ \ \ \ w\ ith\ spaces () (interactive) (message "SPACES"))
>
> (defun cmd-without-spaces () (interactive) (message "NOPE"))
>
> M-x cm SPC ; correctly completes to `cmd'
> SPC ; completes to `cmd '
>
> Since SPC is supposed to complete a word at a time, and since both ` '
> and `-' are word separators, I would expect that there are two
> word completions for the prefix `cmd': `cmd ' and `cmd-'.
>
> So I would expect to see *Completions* displayed, showing the two
> candidates `cmd w ith spaces' and `cmd-without-spaces'.
See the first comment in `completion--try-word-completion':
the function considers that either a space *or* an hyphen will
be used to separate words. The "or" is exclusive.
> Admittedly, this is a corner use case.
Yes -- note that TAB works fine here instead of SPC.
The only place I can think of where this could be a problem
is the info manual (`g' or `i' to go to a node or to find an
index entry.) Still, you're not like to stumble on such case.
I'm for closing this bug until it really hit someone.
next prev parent reply other threads:[~2014-01-07 12:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 17:11 bug#15980: 24.3.50; `minibuffer-complete-word': case where it does not work correctly Drew Adams
2014-01-07 12:04 ` Bastien Guerry [this message]
2014-01-07 17:06 ` Drew Adams
2014-01-07 17:14 ` Bastien
2014-01-07 17:50 ` Drew Adams
2014-01-07 23:37 ` Bastien
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=87d2k4hu77.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=15980@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).