Bug 21239 - xterm does not send escape sequences for numeric keypad
Summary: xterm does not send escape sequences for numeric keypad
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-11-22 13:34 UTC by nvwarr
Modified: 2007-04-18 16:29 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2000-12-04 10:57:10 UTC
Embargoed:


Attachments (Terms of Use)

Description nvwarr 2000-11-22 13:34:38 UTC
Even when "Enable Application Keypad" is selected, xterm is sending normal
numbers rather than escape sequences for the numeric keypad. This breaks
the edt emulation in jed, among other things.

The version of xterm shipped with RH6.2 does not have this problem (even if
used with XFree86 4.0.1)

Comment 1 nvwarr 2000-11-26 09:52:59 UTC
Workaround: add a modifier Num_Lock with xmodmap. It doesn't matter which
modifier it is, nor if it is bound to a key which actually exists. The function
VTInitModifiers in input.c detects the existence of the modifier and then xterm
sends the correct escape sequences, making it possible for jed to work.

It would appear from line 443 of input.c that this behaviour is deliberate. i.e.
if there is no Num_Lock key, never give escape sequences for the numeric keypad,
just the normal numbers. In this case, there is no way for the application to
distinguish between a number key on the main keyboard and one on the numeric
keypad. This behaviour is different from previous versions of xterm. Is there a
good reason for the new behaviour?

Comment 2 Mike A. Harris 2001-03-31 15:16:08 UTC
Not a bug.  This is a configuration issue as you've noted.  xmodmap
is the way to go.


Note You need to log in before you can comment on or make changes to this bug.