unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Vincent Lefevre <vincent@vinc17.net>
Cc: 16645@debbugs.gnu.org
Subject: bug#16645: 24.3; in xterm, keypad = is translated to M-o x
Date: Sat, 28 Mar 2020 01:55:40 +0100	[thread overview]
Message-ID: <87bloh47sj.fsf@stefankangas.se> (raw)
In-Reply-To: <20140205011701.GH10242@xvii.vinc17.org> (Vincent Lefevre's message of "Wed, 5 Feb 2014 02:17:01 +0100")

Vincent Lefevre <vincent@vinc17.net> writes:

> On 2014-02-05 01:15:48 +0100, Vincent Lefevre wrote:
>> 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.
>
> It was due to my XKB settings (only the "=" keypad key gave a
> KP_something keysym due to missing configuration for this key,
> contrary to the other keypad ones).

So it seems like this was not a bug in Emacs?  Could this bug
therefore be closed?

>                                     So, now that the "=" keypad
> key gives a normal "=" keysym, the problem is no longer visible
> in Emacs on my machine. However I'm still wondering about the
> remarks below:

I'm assuming you are here referring the difference between "^[OX" and
"\eOx"?  It seems to me that it's just a difference in how this keysym
is displayed by Emacs and tack.

>> 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])

Best regards,
Stefan Kangas





  reply	other threads:[~2020-03-28  0:55 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
2014-02-05  1:17   ` Vincent Lefevre
2020-03-28  0:55     ` Stefan Kangas [this message]
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

  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=87bloh47sj.fsf@stefankangas.se \
    --to=stefan@marxist.se \
    --cc=16645@debbugs.gnu.org \
    --cc=vincent@vinc17.net \
    /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.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).