Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!psuvax1!julius.cs.uiuc.edu!usc!samsung!uunet!tdatirv!sarima From: sarima@tdatirv.UUCP (Stanley Friesen) Newsgroups: comp.windows.open-look Subject: Re: function keys f1,f11 and f12 Message-ID: <55@tdatirv.UUCP> Date: 9 Nov 90 17:34:40 GMT References: Reply-To: sarima@tdatirv.UUCP (Stanley Friesen) Organization: Teradata Corp., Irvine Lines: 29 I am posting this, since it is likely to be one of the FAQ's for this group. In article writes: >Has anyone been able to figure out how to get function keys >f1,f11 and f12 to work in an xterm under openlook verison 2.0 >on a sparcstation 1. You have two seperate problems here. First, according to the X standard the keysyms for F11 and F12 are the same as the keysyms for L1 and L2. Since the Sparc has both, this is a mapping problem. Openwindows 2.0 has solved this by introducing two vendor-specific keysyms (as allowed by the standard). They are: SunF36 and SunF37 for F11 and F12 respectively. Use these in your translations and all will be well. Second, the defualt Help key for Openwindows 2.0 is F1. This is actually established in the initialization file $OPENWINHOME/lib/Xinitrc. If, as is typical, your Sparc has a key labeled HELP, you do not need this mapping. You may remove it by simply editing $OPENWINHOME/lib/Xinitrc to remove or (better) comment out the xmodmap command. (This will only be a problem if your Openwindows is network installed and some stations lack a HELP key). >On MIT X 11 R4 server they work fine > I'm not quite sure how though - it should be treating L1 and L2 as if they were equivalent to F11 and F12. -- --------------- uunet!tdatirv!sarima (Stanley Friesen)