jon@hitachi.uucp (Jon Ryshpan) (03/23/90)
Has anyone succeeded in getting (user) Key Translations to work on
xterm under Interactive 386/ix X-Windows Version 1.1? I've typed in
the example on p15 of the xterm man page, namely:
*VT100.Translations: #override <Key>F13: keymap(dbx)
*VT100.dbxKeymap.translations: \
<Key>F14: keymap(None) \n\
<Key>F17: string("NEXT") string(0x0d) \n\
<Key>F18: string("STEP") string(0x0d) \n\
<Key>F19: string("CONTINUE") string(0x0d) \n\
<Key>F20: string("PRINT") insert-selection(PRIMARY, CUT_BUFFER0)
with some variations like "VT100" -> "xterm", "F11" -> "F1", etc.
Nothing seems to have any effect. I don't understand the format: what
is "#override" for? why do the lines end with "\n"?
If you've made anything like this work, please reply by email to:
Jonathan Ryshpan <...!uunet!hitachi!jon>
M/S 420 (415) 244-7369
Hitachi America Ltd.
2000 Sierra Pt. Pkwy.
Brisbane CA 94005-1819jrh@mustang.dell.com (James R. Howard) (03/23/90)
In article <290@hitachi.uucp>, jon@hitachi.uucp (Jon Ryshpan) writes: > > Has anyone succeeded in getting (user) Key Translations to work on > xterm under Interactive 386/ix X-Windows Version 1.1? I've typed in > the example on p15 of the xterm man page, namely: > > [ rest deleted ] Yes, try the following: !########### ! Xterm ! xterm*ttyModes: erase ^h xterm*scrollBar: true xterm*termName: vt100 ! make the keypad F1-F4 work like vt100 PF1-PF4 xterm*VT100.Translations: #override <Key>F1: string("OP") \n \ <Key>F2: string("OQ") \n \ <Key>F3: string("OR") \n \ <Key>F4: string("OS") \n \ <Key>F5: string("OT") \n \ <Key>F6: string("OU") \n \ <Key>F7: string("OV") \n \ <Key>F8: string("OW") \n \ <Key>F9: string("OX") \n \ <Key>F10: string("OY") \n ! The ^[ should must be a real escape, not just ^ followed by [