From: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
To: Gregory Heytings <gregory@heytings.org>
Cc: 48153@debbugs.gnu.org, 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, 5 May 2021 14:24:22 +0100 [thread overview]
Message-ID: <CAKDRQS4YnCoKw4juMwY4Gix4xGmGmbQu=GpCv2Sx+-ohdSrSrg@mail.gmail.com> (raw)
In-Reply-To: <70f2eadd5fbd139e3c62@heytings.org>
Ok let me summarize the issue here.
1. On emacs 27, minor mode keybindings will only override the key
bindings given to read-from-minibuffer after the second invocation of
the minibuffer, but doesn't on the first invocation.
2. On emacs 28, minor mode keybindings override the key bindings given
to read-from-minibuffer at all times.
3. But, `minor-mode-overriding-map-alist` does not override the
override in effect in the minibuffer like other buffers.
My expectation is when a keymap is explicitly given to
read-from-minibuffer, the key bindings in it should take precedence,
but it doesn't. As you can see from the snippet from my last email,
both ido-completion-map and test-mode bind to C-k, I expect the C-k
binding in ido-completion-map to take effect inside the minibuffer,
without being overridden by any minor modes in effect inside the
minibuffer. If this is not to be desired, I'd expect setting
minor-mode-overriding-map-alist or the usual key binding lookup search
algorithm to work inside the minibuffer.
Does it make sense?
Jimmy
On Wed, May 5, 2021 at 2:12 PM Gregory Heytings <gregory@heytings.org> wrote:
>
>
> >>> 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:24 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
2021-05-05 13:24 ` Jimmy Yuen Ho Wong [this message]
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='CAKDRQS4YnCoKw4juMwY4Gix4xGmGmbQu=GpCv2Sx+-ohdSrSrg@mail.gmail.com' \
--to=wyuenho@gmail.com \
--cc=48153@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=monnier@iro.umontreal.ca \
/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).