unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.org>
To: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
Cc: 48153@debbugs.gnu.org
Subject: bug#48153: 28.0.50; minor mode keymaps should not override keymap given to read-from-minibuffer
Date: Wed, 05 May 2021 08:09:04 +0000	[thread overview]
Message-ID: <70f2eadd5f48937bb057@heytings.org> (raw)
In-Reply-To: <CAKDRQS5Dm7c7QwwYUK7VZwUWoFfHgKxc3riyEJ3soVQ6Hf_sNQ@mail.gmail.com>


>
> Second of all, in order to get the key map bindings to 
> read-from-minibuffer overridden on emacs 27, it requires quitting from 
> switch-to-buffer, and then C-x b C-h b again to see that C-k is bound to 
> `bad`. In other words, on emacs 27, one has to pop up the minibuffer 
> twice. On emacs 28, just opening the minibuffer the first time will see 
> the key bindings overridden. I guess this is why I say this is a 
> regression on emacs 28 but you said you couldn't reproduce it. I think 
> both versions are wrong, it's just on emacs 28, it's wrong in a more 
> obvious way.
>

Okay, now I finally see what you mean (and I can reproduce it).  Indeed 
this is a recent change in the handling of minibuffers, the first time the 
minibuffer is entered is not anymore different from the other times.

>
> In any case, I'm not sure if the minor mode maps should override the key 
> bindings in the keymap given to read-from-buffer.
>

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.  With the example init file, using

(define-global-minor-mode test-global-mode test-mode (lambda () (or (minibufferp) (test-mode 1))))

works as you want it with both Emacs 27 and 28.





  reply	other threads:[~2021-05-05  8:09 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 [this message]
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
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=70f2eadd5f48937bb057@heytings.org \
    --to=gregory@heytings.org \
    --cc=48153@debbugs.gnu.org \
    --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).