From: Drew Adams <drew.adams@oracle.com>
To: Radon Rosborough <radon.neon@gmail.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 22:46:29 +0000 [thread overview]
Message-ID: <CO6PR10MB5473783F75FFF0CF84005A6BF3D29@CO6PR10MB5473.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CADB4rJE+b3RRLMhbm2-HNtgrpvUb_T=+1euDB2m78-V2mH1iUg@mail.gmail.com>
> a common situation where you want to define bindings
> in a minor mode, but you don't want them to override
> minibuffer bindings.
The global minor mode commands you bind could just
invoke a minibuffer key binding, if any, when there.
Or if you don't want the global minor mode to have
_any_ effect in the minibuffer then you could, in
effect, exclude minibuffers in some way.
But yes, those would be workarounds.
>I can indeed think of situations where you want to
> override a binding globally, so it seems like it
> would be best if there were ways to declare this
> behavior on a per-mode basis.
Sounds reasonable to me. But is it only about key
bindings, or would you be asking (instead? also?)
for a general, easy way to exclude some buffers
from a global minor mode? IOW, instead of it being
entirely global, have it be on (locally) everywhere
except in specified buffers?
next prev parent reply other threads:[~2021-09-06 22:46 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 [this message]
2021-09-06 22:54 ` Radon Rosborough
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CO6PR10MB5473783F75FFF0CF84005A6BF3D29@CO6PR10MB5473.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=50430@debbugs.gnu.org \
--cc=philipk@posteo.net \
--cc=radon.neon@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.