From: Vincent Lefevre <vincent@vinc17.net>
To: 16645@debbugs.gnu.org
Subject: bug#16645: 24.3; in xterm, keypad = is translated to M-o x
Date: Wed, 5 Feb 2014 01:15:48 +0100 [thread overview]
Message-ID: <20140205001548.GE10242@xvii.vinc17.org> (raw)
In-Reply-To: <87k3da2zxl.fsf@xvii.vinc17.org>
On 2014-02-05 00:58:14 +0100, Vincent Lefevre wrote:
> With "emacs -Q -nw" in xterm, the keypad = key (keysym 0xffbd, KP_Equal)
> is translated to M-o x instead of the = character.
According to "tack", the keypad "=" gives:
^[OX Unknown
instead of
= Unknown
Then, I don't know yet whether this is intentional or this is a bug
in xterm. And why the different case for "o" and "x" (uppercase in
tack, lowercase in Emacs)?
In any case, I can see nothing about kp-equal in the xterm.el file.
About the keypad, just:
(define-key map "\eOj" [kp-multiply])
(define-key map "\eOk" [kp-add])
(define-key map "\eOl" [kp-separator])
(define-key map "\eOm" [kp-subtract])
(define-key map "\eOo" [kp-divide])
(define-key map "\eOp" [kp-0])
(define-key map "\eOq" [kp-1])
(define-key map "\eOr" [kp-2])
(define-key map "\eOs" [kp-3])
(define-key map "\eOt" [kp-4])
(define-key map "\eOu" [kp-5])
(define-key map "\eOv" [kp-6])
(define-key map "\eOw" [kp-7])
(define-key map "\eOx" [kp-8])
(define-key map "\eOy" [kp-9])
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
next prev parent reply other threads:[~2014-02-05 0:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 23:58 bug#16645: 24.3; in xterm, keypad = is translated to M-o x Vincent Lefevre
2014-02-05 0:15 ` Vincent Lefevre [this message]
2014-02-05 1:17 ` Vincent Lefevre
2020-03-28 0:55 ` Stefan Kangas
2020-03-28 1:23 ` Vincent Lefevre
2021-09-06 9:36 ` Lars Ingebrigtsen
2021-09-07 9:53 ` Vincent Lefevre
2021-09-08 7:25 ` Lars Ingebrigtsen
2021-09-06 9:59 ` Andreas Schwab
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=20140205001548.GE10242@xvii.vinc17.org \
--to=vincent@vinc17.net \
--cc=16645@debbugs.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.
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.