From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: "'Help-Gnu-Emacs \(help-gnu-emacs@gnu.org\)'" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: Trapping prefixes with universal argument component
Date: Sat, 21 Aug 2021 20:08:45 +0000 [thread overview]
Message-ID: <SJ0PR10MB54885C41073C0028144BD90EF3C29@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87wnoe387m.fsf@zoho.eu>
[-- Attachment #1: Type: text/plain, Size: 823 bytes --]
> > Neither did reassigning M-kp-0
> Hm, maybe it should be put like this: M-<kp-0> ?
> (define-key input-decode-map [M-<kp-0>] nil)
The way to get such things right, assuming that your
keyboard and Emacs can effect the key, is to do this:
1. Use `C-h k' to find out how Emacs itself describes
(names) the key sequence. This tells me:
M-0 (translated from <M-kp-0>) runs the command...
2. Change that to a string by wrapping with "...":
"<M-kp-0>".
3. Pass that to `kbd': (kbd "<M-kp-0>")
That's your answer. And if you want to see what
that ends up being (but you [M-kp-0]don't need to), eval
it: the result is [M-kp-0].
So you can use either (kbd "<M-kp-0>") or [M-kp-0].
Moral: Ask Emacs. Emacs will tell you what to call
any key sequence. Then feed that to `kbd'. CQFD.
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 13841 bytes --]
next prev parent reply other threads:[~2021-08-21 20:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 21:15 Trapping prefixes with universal argument component Tim Johnson
2021-08-20 21:56 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-20 22:37 ` Tim Johnson
2021-08-21 5:08 ` Yuri Khan
2021-08-21 5:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-21 5:39 ` Yuri Khan
2021-08-21 15:18 ` Tim Johnson
2021-08-21 19:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-21 19:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-21 20:08 ` Drew Adams [this message]
2021-08-21 21:03 ` [External] : " Drew Adams
2021-08-21 21:30 ` Tim Johnson
2021-08-21 23:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-22 1:43 ` Drew Adams
2021-08-22 2:51 ` Arthur Miller
2021-08-21 23:19 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-22 1:46 ` Drew Adams
2021-08-21 21:23 ` Tim Johnson
2021-08-21 23:25 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-22 0:42 ` Tim Johnson
2021-08-22 0:51 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-22 8:13 ` Yuri Khan
2021-08-22 8:25 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-22 18:14 ` Trapping prefixes with universal argument component [solved]T Tim Johnson
2021-08-21 19:42 ` Trapping prefixes with universal argument component Emanuel Berg via Users list for the GNU Emacs text editor
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=SJ0PR10MB54885C41073C0028144BD90EF3C29@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).