From: Lars Ingebrigtsen <larsi@gnus.org>
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, 20 Feb 2022 16:22:17 +0100 [thread overview]
Message-ID: <87bkz1pnpy.fsf@gnus.org> (raw)
In-Reply-To: <87muh70y5p.fsf@web.de> (Michael Heerdegen's message of "Mon, 22 Jul 2019 01:24:02 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Anyway, my opinion doesn't matter much. I don't like the behavior of
> space not just inserting a space - I get angry every time this happens.
> I wonder what others do think about it.
I absolutely loathe it, so I have:
(keymap-set minibuffer-local-completion-map "SPC" #'self-insert-command)
(keymap-set minibuffer-local-completion-map "?" #'self-insert-command)
But I don't think this is something we can change at this point.
But I've now added this to the Minibuffer Edit node in the Emacs manual.
I don't think there's anything more to do in this bug report, and I'm
therefore closing it.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-02-20 15:22 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 [this message]
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=87bkz1pnpy.fsf@gnus.org \
--to=larsi@gnus.org \
--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).