Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#30439 - [xterm] 280-1 breaks Home and End keys

Attached to Project: Arch Linux
Opened by Gaetan Bisson (vesath) - Monday, 25 June 2012, 22:16 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 26 June 2012, 16:13 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Andreas Radke (AndyRTR)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

xterm-280-1 breaks the Home and End keys of my Lenovo X220: those keys still work fine in other applications (such as xev), but xterm apparently grabs them and never forwards the event to the underling application (shell, vim, mutt, etc.).

This is introduced by the change "add modifyKeyboard resource to support keypad-modifier changes per request by Thomas Wolff add XK_Home / XK_End to editing-keypad checks". Applying the attached patch (which reverts part of this change) fixes this issue. I am not sure however if this is the right way this should be done...
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Tuesday, 26 June 2012, 16:13 GMT
Reason for closing:  Fixed
Additional comments about closing:  bumped to 281
Comment by Michaël Bruneel (mbruneel) - Monday, 25 June 2012, 22:56 GMT
I confirm, after upgrade, both "Home" and "End" keys are broken in xterm (also with a Lenovo x220).

I tried instructions in the wiki, but doesn't help ...
https://wiki.archlinux.org/index.php/Home_and_End_keys_not_working
Comment by Gaetan Bisson (vesath) - Monday, 25 June 2012, 23:05 GMT
Michaël: If the wiki does not help, why mention it at all? Especially when I already diagnosed the problem and came up with a patch...
Comment by Chris Grams (ChrisNG) - Tuesday, 26 June 2012, 03:14 GMT
I also have this problem with xterm-280-1, using a 'Chicony Electronics Co., Ltd Genius LuxeMate i200' keyboard (according to lsusb) with the 'us' keyboard map.

Setting the xterm to use vt220 keyboard seems to work on the command line and in vim, etc. To make it the default, I placed the following line in my ~/.Xdefaults file:
XTerm*sunKeyboard: true

To try this out before making it the default, start xterm, ctrl+left click in the window, select 'VT220 Keyboard' and try out your home/end keys.
Comment by Natrio (natrio) - Tuesday, 26 June 2012, 09:50 GMT
"sunKeyboard" breaks MC.
"VT220 Keyboard" is not work in "man" and "less" commands.
"XTerm*tcapFunctionKeys: true" seems to be working.
Comment by Andreas Radke (AndyRTR) - Tuesday, 26 June 2012, 14:57 GMT
What is upstream saying about this?
Comment by Natrio (natrio) - Tuesday, 26 June 2012, 15:17 GMT
The Upstream (Thomas E. Dickey) say:
"yes... someone reported this a few hours ago, and I'll be uploading #281 shortly.
thanks"

Loading...