From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
"16528@debbugs.gnu.org" <16528@debbugs.gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Roland Winkler <winkler@gnu.org>
Subject: bug#16528: [External] : bug#16528: 24.3; too many keybindings in minibuffer-local-completion-map
Date: Fri, 20 Aug 2021 21:51:21 +0200 [thread overview]
Message-ID: <87a6lbhp3a.fsf@gmail.com> (raw)
In-Reply-To: <SJ0PR10MB54883B74CFF3B6FE823EC0AEF3C19@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Fri, 20 Aug 2021 16:38:35 +0000")
Drew Adams <drew.adams@oracle.com> writes:
>> But I don't think we can change the defaults here (it would drive (some)
>> people crazy),
>
> Who? Why? How consequential? What about others?
>
> How about one good argument why `?', `SPC', and `C-j'
> shouldn't be self-inserting in the minibuffer, in
> general? If you were designing Emacs today, would
> you make the same argument?
I don't know about good arguments, but FWIW on AZERTY, where '-' is a
pain to reach for, I enjoy 'SPC' doing word completion and inserting
hyphens for Elisp symbols on M-x, C-h v, C-h f, etc.
I'll admit it's a pretty niche use-case, although off the top of my
head, I can't find much uses for self-inserting SPC/?/C-j in the
minibuffer either (Emacs 28's yank-from-kill-ring comes to mind, but '?'
and 'SPC' are already self-inserting there[1]).
[1] https://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/simple.el?id=00a9c50ad7c82f72b422100624f7f125d717c00f#n5793
next prev parent reply other threads:[~2021-08-20 19:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 13:06 bug#16528: 24.3; too many keybindings in minibuffer-local-completion-map Roland Winkler
2014-01-23 18:03 ` Stefan Monnier
2014-01-23 19:02 ` Roland Winkler
2014-01-23 19:16 ` Drew Adams
2021-08-20 15:00 ` Lars Ingebrigtsen
2021-08-20 16:38 ` bug#16528: [External] : " Drew Adams
2021-08-20 19:51 ` Kévin Le Gouguec [this message]
2021-08-20 21:11 ` Drew Adams
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=87a6lbhp3a.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=16528@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=winkler@gnu.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 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).