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
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
|
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... 
wtf.patch
(0.3 KiB)
|
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
Tuesday, 26 June 2012, 16:13 GMT
Reason for closing: Fixed
Additional comments about closing: bumped to 281
I tried instructions in the wiki, but doesn't help ...
https://wiki.archlinux.org/index.php/Home_and_End_keys_not_working
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.
"VT220 Keyboard" is not work in "man" and "less" commands.
"XTerm*tcapFunctionKeys: true" seems to be working.
"yes... someone reported this a few hours ago, and I'll be uploading #281 shortly.
thanks"