home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases.ingres
- Path: sparky!uunet!UB.com!pacbell.com!ames!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!howland.reston.ans.net!usc!news.aero.org!speedy.aero.org!ariel.aero.org!amiranda
- From: amiranda@ariel.aero.org (Ann Miranda)
- Subject: Sun Sparc 10 / Sun5 keyboard mappings
- Message-ID: <1993Jan28.145848.20160@speedy.aero.org>
- Sender: news@speedy.aero.org
- Nntp-Posting-Host: ariel.aero.org
- Organization: The Aerospace Corporation; El Segundo, CA
- Date: Thu, 28 Jan 1993 14:58:48 GMT
- Lines: 115
-
- I recently posted for help on keymappings for the new sun5 keyboard for
- sparc 10s. I've had a lot of response -- mostly people with the same problem,
- asking for help also.
-
- I got a response from an Ingres person, who sent me some keymaps to
- include in the .Xdefaults and .xmodmaprc files. I am including them in this post,
- for people to try. I tried the keymaps, but still have some problems.
-
- Ingres says the problem is due to Motif, but I have it in both Motif and
- Openwindows. Also,the keymaps they gave are for TERM_INGRES = vt100f, and it
- is not obvious what keys you must press on the keyboard to access the
- corresponding functions-- ie. like the "PF2" key doesn't exist on the sun5
- keyboard, and I can't figure out which key is supposed to be that key.
-
- I have been told that to map a new keyboard completely is a laborious
- task! But I really want to use my keyboard as a sun5 keyboard, not a vt100f
- keyboard. If I get anywhere, I'll post again.
-
- If anyone tries this information from Ingres, and it works, please let
- me know -- I may be doing something wrong. (At least a vt100f is better than
- a vt100, which does work on the sparc 10, but is a real pain!)
-
- Ann Miranda
- amiranda@ariel.aero.org
-
-
- Following is the info I received from Ingres (with credit to Scott Stevens
- and Jeff Bryson)
-
- -----begin file -------
-
- CAUTION: The following is not supported, as of 12/10/92:
-
- The problem is not with the termcap definitions for INGRES, but rather
- with X/MOTIF termcap definitions. NOTE THAT WITHOUT THE MODIFICATIONS
- BELOW, THE ARROW KEYS DO NOT EVEN WORK IN THE "vi" EDITOR.
-
- These modifications are for the X/MOTIF environment only. Set
- TERM_INGRES to "vt100f".
-
- ------------------- cut here and put near top of X11R4init --------
- xmodmap -e "keysym BackSpace = Delete"
- xmodmap ~/.xmodmaprc
- ------------------- cut here and call .xmodmaprc ----------------
- keycode 8 = F11 Cancel
- keycode 10 = F12 Redo
- keycode 20 = Alt_R
- keycode 27 = Up
- keycode 29 = F22 Print
- keycode 30 = F23 Scroll_Lock
- keycode 31 = Left
- keycode 33 = F14 Undo
- keycode 34 = Down
- keycode 35 = Right
- keycode 51 = Insert
- keycode 59 = Home
- keycode 76 = F28 KP_8
- keycode 81 = End
- keycode 98 = F30 KP_4
- keycode 99 = F31 KP_5
- keycode 100 = F32 KP_6
- keycode 118 =
- keycode 119 = R13 KP_1
- keycode 120 = F34 KP_2
- keycode 121 = F35 KP_3
- keycode 103 = Prior
- keycode 130 = Next
- ------------------- cut here and put in .Xdefaults --------------
- /*
- ** These translations cause some of the Sun Type-5 Keyboard keys to
- ** generate strings making them equivalent to various VT100 keys.
- **
- ** Sun VT100
- ** --- -----
- ** NumLock PF1
- ** / PF2
- ** * PF3
- ** - PF4
- ** PageUp ,
- ** PageDn -
- */
- XTerm.VT100.Translations: #override \
- <Key>Help: string(0x1b) string("[28~") \n\
- <Key>F1: string(0x1b) string("[18~") \n\
- <Key>F2: string(0x1b) string("[19~") \n\
- <Key>F3: string(0x1b) string("[20~") \n\
- <Key>F4: string(0x1b) string("[21~") \n\
- <Key>F5: string(0x1b) string("[23~") \n\
- <Key>F6: string(0x1b) string("[24~") \n\
- <Key>F7: string(0x1b) string("[25~") \n\
- <Key>F8: string(0x1b) string("[26~") \n\
- <Key>F9: string(0x1b) string("[31~") \n\
- <Key>F10: string(0x1b) string("[32~") \n\
- <Key>F11: string(0x1b) string("[33~") \n\
- <Key>F12: string(0x1b) string("[34~") \n\
- <Key>Num_Lock: string(0x1b) string("OP") \n\
- <Key>KP_Equal: string(0x1b) string("OQ") \n\
- <Key>KP_Multiply: string(0x1b) string("OR") \n\
- <Key>KP_Subtract: string(0x1b) string("OS") \n\
- <Key>Prior: string(0x1b) string("Om") \n\
- <Key>Next: string(0x1b) string("Ol") \n\
- <Key>KP_7: string(0x1b) string("Ow") \n\
- <Key>KP_8: string(0x1b) string("Ox") \n\
- <Key>KP_9: string(0x1b) string("Oy") \n\
- <Key>KP_4: string(0x1b) string("Ot") \n\
- <Key>KP_5: string(0x1b) string("Ou") \n\
- <Key>KP_6: string(0x1b) string("Ov") \n\
- <Key>KP_1: string(0x1b) string("Oq") \n\
- <Key>KP_2: string(0x1b) string("Or") \n\
- <Key>KP_3: string(0x1b) string("Os") \n\
- <Key>KP_0: string(0x1b) string("Op") \n\
- <Key>KP_Decimal: string(0x1b) string("On") \n\
- <Key>KP_Enter: string(0x1b) string("OM") \n
-
-
-