From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48153@debbugs.gnu.org, Jimmy Yuen Ho Wong <wyuenho@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#48153: 28.0.50; minor mode keymaps should not override keymap given to read-from-minibuffer
Date: Wed, 05 May 2021 13:12:49 +0000 [thread overview]
Message-ID: <70f2eadd5fbd139e3c62@heytings.org> (raw)
In-Reply-To: <83r1il2x7t.fsf@gnu.org>
>>> Why would they not? The minibuffer behaves, in that respect, like any
>>> other buffer. Note that they do so only when the minor mode is
>>> enabled in the minibuffer.
>>
>> Because the minibuffer does not behave like any other buffers. Setting
>> `minor-mode-overriding-map-alist` has no effect, so I think either the
>> minibuffer really needs to behave like any other buffer, or
>> special-cased and documented the ways it differs from regular buffers.
>
> I admit that I've lost the context in this discussion. I'm CC'ing
> Stefan in the hope he could tell whether we do or don't have a problem
> here; if Stefan is unable to do that, either, we will unfortunately have
> to get back to the beginning and explain what kind of problems the
> current behavior causes. Because in general what Jimmy described in the
> original report sounds the expected behavior to me.
>
I admit I'm lost, too. The description of the problem has changed several
times, and what was described in the original report is the actual
behavior. Of course I may be missing something; I'm not fortunate enough
to have a crystal ball, like Stefan ;-)
next prev parent reply other threads:[~2021-05-05 13:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 6:58 bug#48153: 28.0.50; minor mode keymaps should not override keymap given to read-from-minibuffer Jimmy Yuen Ho Wong
2021-05-03 15:15 ` Gregory Heytings
2021-05-04 12:53 ` Jimmy Yuen Ho Wong
2021-05-04 13:13 ` Gregory Heytings
2021-05-04 13:52 ` Jimmy Yuen Ho Wong
2021-05-04 14:02 ` Gregory Heytings
2021-05-04 14:29 ` Gregory Heytings
2021-05-04 16:15 ` Jimmy Yuen Ho Wong
2021-05-04 16:36 ` Gregory Heytings
2021-05-04 22:40 ` Jimmy Yuen Ho Wong
2021-05-05 8:09 ` Gregory Heytings
2021-05-05 9:10 ` Jimmy Yuen Ho Wong
2021-05-05 12:15 ` Eli Zaretskii
2021-05-05 13:12 ` Gregory Heytings [this message]
2021-05-05 13:24 ` Jimmy Yuen Ho Wong
2021-05-05 14:17 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-06 10:55 ` Jimmy Yuen Ho Wong
2021-05-09 14:57 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-05 13:06 ` Gregory Heytings
2021-05-05 14:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=70f2eadd5fbd139e3c62@heytings.org \
--to=gregory@heytings.org \
--cc=48153@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=wyuenho@gmail.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).