Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!dent.Berkeley.EDU!davidh
From: davidh@dent.Berkeley.EDU (David S. Harrison)
Newsgroups: comp.windows.x
Subject: Meta Keys on UWS 2.0 and Xt Intrinsics
Keywords: Meta, Xt
Message-ID: <10369@pasteur.Berkeley.EDU>
Date: 26 Feb 89 01:15:15 GMT
Sender: news@pasteur.Berkeley.EDU
Reply-To: davidh@ic.Berkeley.EDU
Followup-To: comp.widnows.x
Organization: UC Berkeley Electronics Research Lab
Lines: 27

When I recently upgraded to DEC UWS 2.0 from X11R3,  I noticed
that meta-key bindings in the Xaw text widget no longer worked
(e.g. when I typed Meta-i,  an `i' was inserted into the buffer).
After some exploratory debugging,  I realized that the Xt Intrinsics
concept of Meta is not always portable.  The following quote from
X Toolkit Intrinsics - C Language Interface (Release 3) explains

	For example, ``m'' or ``Meta'' means any modifier bit
	mapping to a keycode whose keysym list contains
	XK_Meta_L or XK_Meta_R.

Unfortunately,  in the default mapping provided by the UWS 2.0
server,  only one keysym is defined for the ``compose character''
key: Alt_L.  Since this is neither XK_Meta_L or XK_Meta_R,  Xt
translation tables do not consider this to be ``Meta''.  Fortunately,
xmodmap comes to the rescue.  If you are running UWS 2.0,  the following
command fixes the problem:

	xmodmap -e 'keycode 0xb1 = Alt_L Meta_L'

More importantly,  should this be considered a bug in the UWS 2.0 server
or is it within the rights of the server implentor to define whatever 
mapping they feel is appropriate?

			David Harrison
			UC Berkeley Electronics Research Lab
			(davidh@ic.Berkeley.EDU, ...!ucbvax!ucbcad!davidh)