From: Bryan Wright <bkw1a@ayesha.phys.virginia.edu>
To: help-gnu-emacs@gnu.org
Subject: Wrong keypad bindings for some keys in emacs 23.1 under CentOS 6
Date: Tue, 13 Dec 2011 19:07:16 +0000 (UTC) [thread overview]
Message-ID: <loom.20111213T195750-99@post.gmane.org> (raw)
Hi folks,
I'm preparing to transition some machines from CentOS 5.7 (with emacs 21.4)
to CentOS 6 (with emacs 23.1). Some of our users rely on using the non-window
version of emacs and the tpu-edt package, which makes use of the keypad keys.
I find that emacs 23.1 under CentOS 6 has some mistakes in the key bindings
for the keypad. For example, the escape sequence "\eOQ" should be bound to
[kp-f2], but it's really bound to [f2], and the sequence "\eOn" should be bound
to [kp-decimal], but it's not bound to anything at all.
Can anybody point me to a quick way to remap these keys? I've been playing
around with "define-key" and "global-set-key", but haven't had any luck yet.
Thanks in advance,
Bryan
next reply other threads:[~2011-12-13 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 19:07 Bryan Wright [this message]
2011-12-13 21:37 ` Wrong keypad bindings for some keys in emacs 23.1 under CentOS 6 Philipp Haselwarter
2011-12-14 15:54 ` Bryan Wright
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=loom.20111213T195750-99@post.gmane.org \
--to=bkw1a@ayesha.phys.virginia.edu \
--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).