[comp.windows.x] VT220 keymap for Xterm on HP/Apollo 9000-400

levitch@ssd31.mdcbbs.com (02/07/91)

I'm trying to map the Xterm keys on an HP/Apollo 9000-400 to be usable
on a DEC vt220.  I used 'xmodmap' with a keymap file containing the
following:

    keysym KP_Multiply = KP_F1
    keysym KP_Divide = KP_F2
    keysym KP_Add = KP_F3
    keysym KP_Subtract = KP_F4
    keysym KP_Enter = KP_Subtract
    keysym KP_Tab = KP_Enter
    keysym BackSpace = Delete

this seemed to work just fine, until I created another HPterm or Xterm
and it still had the vt220 keymappings.  Why do the vt220 keymaps remain?
How do I set the vt220 keymaps ONLY for one instance of Xterm?

Thanks, (in advance)

-- 
! Edward Levitch                  ! Human:    714/896-3311 x70256             !
! McDonnell Douglas Space Systems ! Internet: levitch@ssd31.mdcbbs.com        !
! Huntington Beach, CA 92647      ! uucp:     uunet!ssd31.mdcbbs.com!levitch  !
!"He's seeing monsters. He's loosing his mind and he feels it going."-Puppies-!

mouse@lightning.mcrcim.mcgill.EDU (02/08/91)

> I'm trying to map the Xterm keys on an HP/Apollo 9000-400 to be
> usable on a DEC vt220.  I used 'xmodmap' with a keymap file
> containing the following:

>     keysym KP_Multiply = KP_F1
>     keysym KP_Divide = KP_F2
[...etc...]

> this seemed to work just fine, until I created another HPterm or
> Xterm and it still had the vt220 keymappings.  Why do the vt220
> keymaps remain?

Why would they go away?  You told the server that the key that used to
correspond to KP_Multiply was to correspond to KP_F1; naturally, when
you press it, you get a KP_F1 event, regardless of which client is
listening to the keystroke.

> How do I set the vt220 keymaps ONLY for one instance of Xterm?

I'm not sure.  You can probably do something with the -name and -class
options and the Translations resource, but I'll let someone better
versed in toolkit magic handle that side of it.

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu