From: Marcin Borkowski <mbork@mbork.pl>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How does command remapping actually work?
Date: Fri, 30 Jul 2021 18:17:49 +0200 [thread overview]
Message-ID: <87r1ffdbde.fsf@mbork.pl> (raw)
In-Reply-To: <83r1fhskmh.fsf@gnu.org>
On 2021-07-29, at 08:24, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Marcin Borkowski <mbork@mbork.pl>
>> Date: Thu, 29 Jul 2021 07:12:50 +0200
>>
>> I experimented a bit with command remapping, and it's great - but how
>> does it actually work? I mean, apparently it doesn't change the keymap,
>> and it's not stored in its symbol plist, so where is the remapping info
>> actually stored? IOW, what is changed when I evaluate things like
>>
>> (define-key my-mode-map [remap kill-line] 'my-kill-line)
>
> The 'remap' pseudo-key works via special handling in the low-level
> keymap code, see the source of where-is-internal in keymap.c (search
> for "Qremap").
Thanks!
--
Marcin Borkowski
http://mbork.pl
next prev parent reply other threads:[~2021-07-30 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 5:12 How does command remapping actually work? Marcin Borkowski
2021-07-29 6:24 ` Eli Zaretskii
2021-07-30 16:17 ` Marcin Borkowski [this message]
2021-07-29 22:34 ` Michael Heerdegen
2021-07-30 16:17 ` Marcin Borkowski
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=87r1ffdbde.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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.
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).