From: Ihor Radchenko <yantar92@posteo.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to handle both minor mode and major mode remapping a command?
Date: Sat, 21 Dec 2024 12:00:40 +0000 [thread overview]
Message-ID: <87v7vd5jpz.fsf@localhost> (raw)
In-Reply-To: <875xnfbh2g.fsf@web.de>
Michael Heerdegen <michael_heerdegen@web.de> writes:
>> What I was thinking about is some way for command remapping to:
>>
>> 1. remap overriding minor modes
>> 2. be able to access commands (possible remapped) that are shadowed by
>> current remapping
>>
>> Maybe what I want is advice flexibility for keymaps. (not sure)
>
> What would one be able to do using that imagined mechanism that one
> cannot do with `add-function'?
My main problem with the idea of kill-line-function is that I do not
fully understand how it can work in all cases. Specifically, imagine
what happens when visual-line-mode is activated _after_ Org mode is
activated. How can Org mode make sure that kill-visual-line does not
unconditionally override Org bindings?
--
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2024-12-21 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 11:53 Bug: org-kill-line shouldn't assume visual-line-mode means kill-visual-line Nathan Collins
2024-12-15 10:48 ` How to handle both minor mode and major mode remapping a command? (was: Bug: org-kill-line shouldn't assume visual-line-mode means kill-visual-line) Ihor Radchenko
2024-12-17 17:33 ` How to handle both minor mode and major mode remapping a command? Michael Heerdegen
2024-12-19 17:38 ` Ihor Radchenko
2024-12-19 19:36 ` Michael Heerdegen
2024-12-21 12:00 ` Ihor Radchenko [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v7vd5jpz.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=michael_heerdegen@web.de \
/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/org-mode.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).