From: Drew Adams <drew.adams@oracle.com>
To: Jean Louis <bugs@gnu.support>, 36745@debbugs.gnu.org
Subject: bug#36745: 27.0.50; completing-read with require-match nil does not accept spaces
Date: Sat, 20 Jul 2019 20:14:43 +0000 (UTC) [thread overview]
Message-ID: <036a63d2-bc36-4e5e-8de5-e45f4d189469@default> (raw)
In-Reply-To: <86blxoil4q.fsf@protected.rcdrun.com>
> completing-read is not accepting spaces when require-match is nil
>
> I have discovered I could use C-q SPACE to enter space and get any
> input
> such as "two words"
>
> (completing-read "Hello: " '("Something here" "more here") nil nil)
>
> The above function is accepting any input, not just completions, but
> spaces cannot be entered.
>
> I think that it is not logical if it says "any input" that spaces
> cannot be entered and it is in that sense possible bug.
FWIW: By default, both `?' and `SPC' are
self-inserting for completion in Icicles
(and have been since 2004).
But this is configurable, with option
`icicle-completion-key-bindings'.
https://www.emacswiki.org/emacs/Icicles_-_Key_Bindings#MinibufferBindings
next prev parent reply other threads:[~2019-07-20 20:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 19:03 bug#36745: 27.0.50; completing-read with require-match nil does not accept spaces Jean Louis
2019-07-20 20:14 ` Drew Adams [this message]
2019-07-20 21:02 ` Jean Louis
2019-07-20 21:52 ` Drew Adams
2019-07-20 23:13 ` Jean Louis
2019-07-21 0:04 ` Drew Adams
2019-07-21 7:34 ` Jean Louis
2019-07-20 23:40 ` Michael Heerdegen
2019-07-21 7:27 ` Jean Louis
2019-07-21 9:55 ` Basil L. Contovounesios
2019-07-21 19:53 ` Michael Heerdegen
2019-07-21 23:24 ` Michael Heerdegen
2019-07-22 0:03 ` Drew Adams
2022-02-20 15:22 ` Lars Ingebrigtsen
2022-02-20 22:24 ` bug#36745: [External] : " Drew Adams
2019-07-21 9:54 ` Basil L. Contovounesios
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=036a63d2-bc36-4e5e-8de5-e45f4d189469@default \
--to=drew.adams@oracle.com \
--cc=36745@debbugs.gnu.org \
--cc=bugs@gnu.support \
/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).