Dear Richard,
you'd put me on the right track, even though you expected the location of my
problem at the wrong location. The issue is xterm as such. You need to edit
/usr/lib/X11/app-defaults/XTerm. There is a chapter:
XTerm*VT100.Translations: #override
where I added two lines:
Ctrl<Key>Left: string(0x01) \n\
Ctrl<Key>Right: string(0x06) \n\
(knowing that the apropriate assignments of prevword ^A and nextword ^F had
been entered in joerc) and I got what I wanted. Similar, for the normal
keyboard I had to enter (but this one I knew before):
control keycode 105 = Control_a
control keycode 106 = Control_f
in /usr/lib/kbd/keymaps/i386/include/linux-keys-bare.inc. Anyway, many thanks.
You took me on the right trace.
Dieter
On 10-Feb-99 Richard Andrews wrote:
> This is could be a window manager problem. Some window managers grab the
> CTRL-Left/Right or ALT-Left/Right key combinations which means your
> applications (including xterms) never receive the signal. You can usually
-----------------------------------------------------------
E-Mail: Dieter's Standardbenutzer <[EMAIL PROTECTED]>
Date: 10-Feb-99
Time: 21:10:19 |
\
/\_/\ |
| ~x~ |/-----\ /
\ /- \_/
^^__ _ / _ ____ /
<��__ \- \_/ | |/ | |
|| || _| _| _| _|
if you really want to see the pictures above - use some font
with constant spacing like courier! :-)
-----------------------------------------------------------
