Re: Bug#2313: xterm keymapping problems suspected
Richard Kaszeta writes:
> Is this a bug or a misfeature...? Xfree inherits many of the
> keymappings from the spawning tty, and on most linux distributions
> (including debian) the default keymappings for the text console (US
> keyboard maps at least) map both these keys to the same value...
>
> For example, /usr/lib/kdb/keytables/us.map on default 0.93R6 systems
> maps both keycodes 9 and 111 to the same code (mostly, one is mapped
> to Delete and one to Remove, not really sure the difference but by the
> time X gets done they are the same).
There's a huge difference: Under X backspace is ^H, under console linux it's
^?. Well, at least that's what it's supposed to be.
> Shouldn't this be fixed? Would also cut down on the 'Backspace
> doesn't work in Netscape' complaints... :)
Where's the problem with netscape? From a HOWTO:
! To make Backspace delete-previous-character and Delete
! delete-next-character in Motif applications
*XmText.translations: #override \n\
~a <Key>osfBackSpace: delete-previous-character() \n\
~a <Key>osfDelete: delete-next-character() \n\
a <Key>osfDelete: delete-previous-word() \n\
c <Key>d: delete-next-character() \n\
a <Key>d: delete-next-word() \n\
c <Key>a: beginning-of-line() \n\
c <Key>e: end-of-line() \n\
c <Key>k: delete-to-end-of-line() \n\
a <Key>Left: backward-word() \n\
a <Key>Right: forward-word()
*XmTextField.translations: #override \n\
~a <Key>osfBackSpace: delete-previous-character() \n\
~a <Key>osfDelete: delete-next-character() \n\
a <Key>osfDelete: delete-previous-word() \n\
c <Key>d: delete-next-character() \n\
a <Key>d: delete-next-word() \n\
c <Key>a: beginning-of-line() \n\
c <Key>e: end-of-line() \n\
c <Key>k: delete-to-end-of-line() \n\
a <Key>Left: backward-word() \n\
a <Key>Right: forward-word()
That should work, doesn't it?
Michael
--
Michael Meskes
Lehrstuhl fuer angewandte Mathematik insb. Informatik
RWTH-Aachen, D-52056 Aachen, Germany
email: meskes@informatik.rwth-aachen.de
Reply to: