Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!ucsd!ucbvax!ucdavis!csusac!unify!Unify.com!jeff From: jeff@Unify.com (Jeff Mischkinsky) Newsgroups: comp.windows.open-look Subject: Re: function keys f1,f11 and f12 Message-ID: <1990Nov13.182018@Unify.com> Date: 14 Nov 90 02:20:18 GMT References: <1990Nov8.083925@Unify.com> Sender: news@Unify.Com (news admin) Reply-To: jeff@Unify.com (Jeff Mischkinsky) Organization: Unify Corporation, Sacramento, CA, USA Lines: 33 In article <1990Nov8.083925@Unify.com>, grp@Unify.com (Greg Pasquariello) writes: > In article , uunet!nmri!loach!alex > (Alexander G. Macur) 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. > > > > On MIT X 11 R4 server they work fine > > > > First you have to understand keys vs keysysms. Whenever a key > is pressed, the X server takes that key, and maps it to a keysym. > The keysym is what xterm thinks was really pressed. For example > pressing the F3 Key causes the server to map an F3 keysym, and > everything works just fine. > > The problem is that the xnews server maps the sun keys in an > odd way. By default, it maps the L1 and L2 keys (on the left of > the keyboard) to the F11 and F12 keysyms, and it maps the F1 key > to the Help keysym. It then maps the F11 and F12 keys to the > SunF36 and SunF37 keysysms. Don't ask me why, 'cuz I can't tell > you. The reason is that the standard X keysyms only go up to F35. Since Sun has more than that, they had to roll their own. -- Jeff Mischkinsky internet: jeff@unify.com Unify Corporation ...!{pyramid,csusac}!unify!jeff 3870 Rosin Court voice: (916) 920-9092 fax: (916) 921-5340 Sacramento, CA 95834 ICBMS: 38 38 40 N / 120 28 10 W