Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!usc!elroy.jpl.nasa.gov!ames!amelia!chiu
From: chiu@amelia.nas.nasa.gov (Tsau Chiu)
Newsgroups: comp.sys.next
Subject: Re: Solution to VT100 keypad query (Thanks J. Schneider!)
Message-ID: <5325@amelia.nas.nasa.gov>
Date: 24 Mar 90 19:36:23 GMT
References: <17998@oregon.uoregon.edu>
Reply-To: chiu@amelia.nas.nasa.gov (Ing-Tsau Chiu)
Distribution: usa
Organization: NASA Ames Research Center, Moffett Field, CA
Lines: 35

In article <17998@oregon.uoregon.edu> JOE@oregon.uoregon.edu (Joe St Sauver) writes:
     <info about vt100 keymap deleted>
>>I added the following line to my .cshrc file
>>
>>alias vt100-keys xmodmap /Users/schneidj/.vt100-keymap
>>
>>keycode 21=KP_Separator
>>keycode 38=KP_F1
>>keycode 39=KP_F2
>>keycode 40=KP_F3
>>keycode 37=KP_F4

To restore the keymap for NeXT keyboard, save the following five lines
into a file, say ~/.xterm-keymap.

keycode 21=KP_Add
keycode 38=quoteleft asciitilde
keycode 39=KP_Equal
keycode 40=KP_Divide
keycode 37=KP_Multiply

Then add the following to your aliases -

alias xterm-keys xmodmap ~/.xterm-keymap

When you need to restore the NeXT key mapping, just run the command,

     xterm-keys

from a shell.

-- 
--
Ing-Tsau Chiu                       chiu@amelia.nas.nasa.gov
                                    chiu@wk25.nas.nasa.gov