From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 36745@debbugs.gnu.org, Jean Louis <bugs@gnu.support>
Subject: bug#36745: 27.0.50; completing-read with require-match nil does not accept spaces
Date: Sun, 21 Jul 2019 10:54:20 +0100 [thread overview]
Message-ID: <87ef2jr9v7.fsf@tcd.ie> (raw)
In-Reply-To: <87o91oxojr.fsf@web.de> (Michael Heerdegen's message of "Sun, 21 Jul 2019 01:40:40 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> So I don't see any bug in the strict sense. OTOH I think it would be
> good to speak out that SPC is special, and mention the C-q SPC
> workaround, at least in the manual (if we don't do this already - do
> we?).
We do, see (info "(emacs) Minibuffer Edit"):
Inside a minibuffer, the keys <TAB>, <SPC>, and ‘?’ are often bound
to “completion commands”, which allow you to easily fill in the desired
text without typing all of it. *Note Completion. As with <RET>, you
can use ‘C-q’ to insert a <TAB>, <SPC>, or ‘?’ character.
and (info "(emacs) Completion Commands").
--
Basil
prev parent reply other threads:[~2019-07-21 9:54 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
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 [this message]
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=87ef2jr9v7.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=36745@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=michael_heerdegen@web.de \
/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).