From: Radon Rosborough <radon.neon@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Philip Kaludercic <philipk@posteo.net>,
"50430@debbugs.gnu.org" <50430@debbugs.gnu.org>
Subject: bug#50430: [External] : bug#50430: windmove bindings now override org-read-date
Date: Mon, 6 Sep 2021 15:54:51 -0700 [thread overview]
Message-ID: <CADB4rJHkTgsGgQSPGY48MqrPZuU_Xr7pfHDqy=aOChKkemMjMA@mail.gmail.com> (raw)
In-Reply-To: <CO6PR10MB5473783F75FFF0CF84005A6BF3D29@CO6PR10MB5473.namprd10.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
> The global minor mode commands you bind could just
> invoke a minibuffer key binding
How? What I'm trying to do is avoid overriding a minibuffer key binding
established by another package, which I don't control.
> if you don't want the global minor mode to have
> _any_ effect in the minibuffer
No, generally the desired behavior for these use cases is that the
keybinding will by default be active in the minibuffer, unless
minibuffer-local-map happens to override that key, in which case
minibuffer-local-map should be preferred.
> is it only about key bindings
That's the problem I face, yes. Per my above comment, just conditionally
disabling the minor mode doesn't actually solve the problem. Unless you
were to conditionally disable it by scanning minibuffer-local-map for a
specific set of keybindings, which feels somewhat horrifying.
More generally though, it would be really nice if there were a way to
specify the numeric priority of a keybinding. Currently, minor modes are
unconditionally preferred over major modes and minibuffer bindings, which
are unconditionally preferred over global bindings. Usually this is what
you want, but when it isn't, the workarounds feel pretty hacky.
[-- Attachment #2: Type: text/html, Size: 1420 bytes --]
next prev parent reply other threads:[~2021-09-06 22:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 13:56 bug#50430: windmove bindings now override org-read-date Radon Rosborough
2021-09-06 14:18 ` Philip Kaludercic
2021-09-06 14:29 ` Radon Rosborough
2021-09-06 22:07 ` bug#50430: [External] : " Drew Adams
2021-09-06 22:34 ` Radon Rosborough
2021-09-06 22:46 ` Drew Adams
2021-09-06 22:54 ` Radon Rosborough [this message]
2021-09-07 7:49 ` Philip Kaludercic
2021-09-06 15:38 ` Juri Linkov
2022-08-23 16:41 ` Lars Ingebrigtsen
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='CADB4rJHkTgsGgQSPGY48MqrPZuU_Xr7pfHDqy=aOChKkemMjMA@mail.gmail.com' \
--to=radon.neon@gmail.com \
--cc=50430@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=philipk@posteo.net \
/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).