gklaass@yunexus.yorku.ca (Gary Klaassen) (10/13/90)
We have been using xterm supplied with Irix 3.2.1 with the -ibmkbd option to provide a full vt100 keypad when using the edt-emulation mode of gnu emacs on sgi's and other unix machines and when using the edt editor itself on a Vax running VMS. The -ibmkbd option is no longer supported by the xterm that comes with Irix 3.3.1. We tried the options 'enable application cursor keys/keypad' in the xterm VT options menu but they only enable a small number of the needed keys. Does anyone have a solution? Thanks, G. Klaassen
root@sgzh.uucp (Bruno Pape) (10/14/90)
In article <16123@yunexus.YorkU.CA> gklaass@yunexus.yorku.ca (Gary Klaassen) writes: >We have been using xterm supplied with Irix 3.2.1 with the -ibmkbd option >to provide a full vt100 keypad when using >the edt-emulation mode of gnu emacs on sgi's and other unix machines >and when using the edt editor itself on a Vax running VMS. > >The -ibmkbd option is no longer supported by the xterm that comes with Irix >3.3.1. We tried the options 'enable application cursor keys/keypad' >in the xterm VT options menu but they only enable a small number of >the needed keys. > >Does anyone have a solution? Thanks, G. Klaassen There is no replacement. There is a bug report on this and the scr number is 10899. A workaround is to copy xterm from 3.2 to a 3.3.x system. But, you need to kill Xsgi and restart it with bc flag (plus the flags it was originally started with). As quoted from my contact in Mountain View. Bruno Pape
Chris L. Fouts (10/15/90)
> > We have been using xterm supplied with Irix 3.2.1 with the -ibmkbd option > to provide a full vt100 keypad when using > the edt-emulation mode of gnu emacs on sgi's and other unix machines > and when using the edt editor itself on a Vax running VMS. > > The -ibmkbd option is no longer supported by the xterm that comes with Irix > 3.3.1. We tried the options 'enable application cursor keys/keypad' > in the xterm VT options menu but they only enable a small number of > the needed keys. > > Does anyone have a solution? Thanks, G. Klaassen > Well this isn't a total solution, but it may get you started. I have the following lines in my ~/.Xdefaults file to map the top row of the keypad as well as the backspace key. XTerm*VT100.Translations: #override \ <Key>BackSpace: string(0x7f) \n\ <Key>Num_Lock: string(0x1b) string("OP") \n\ <Key>KP_Divide: string(0x1b) string("OQ") \n\ <Key>KP_Multiply: string(0x1b) string("OR") \n\ <Key>KP_Subtract: string(0x1b) string("OS") \n\ -- Chris L. Fouts Email: fouts@inetg1.arco.com Systems Engineer Phone: 214-754-3850 Silicon Graphics Computer Systems