[4943] in testers
Re: keymapping problems on SunBlade keyboards
daemon@ATHENA.MIT.EDU (Mitchell E Berger)
Tue Jul 3 23:43:37 2001
Message-Id: <200107040343.XAA26229@byte-me.mit.edu>
To: Jonathon Weiss <jweiss@MIT.EDU>
cc: Mitchell E Berger <mitchb@MIT.EDU>, testers@MIT.EDU
In-Reply-To: Your message of "Tue, 03 Jul 2001 16:10:36 EDT."
<200107032010.QAA04442@the-other-woman.mit.edu>
Date: Tue, 03 Jul 2001 23:43:34 -0400
From: Mitchell E Berger <mitchb@MIT.EDU>
> this is almost certainly a USB keyboard issue and related to [4723] in
> testers.
Yes, I should have caught the fact that it had already been mentioned. Sorry
for missing it. I've worked on the problem a bit, and it turns out that we
already have a kludge in place to run xmodmap on a file called AthenaMods
on Suns. I have come up with a slightly modified version of the file that
will make the SunBlades behave identically to the other Suns with respect to
the bottom row of keys. Unfortunately, because the keycodes are different,
using this file on non-Blades causes errors and doesn't work. I'm not sure
whether avoiding startup tasks that are more specific than platform (i.e
UltraSparc IIe (Blade) as opposed to sun4) or avoiding inconsistent keyboard
behavior is more important. I'd like to see the keyboards function the same
way, but I'd understand if general feeling is that effecting that would be
too much of a kludge. If it's wanted, here's a Blade-friendly file for use
with xmodmap:
Mitch
! The SunBlade 100s come with USB keyboards and map the left Alt key
! differently than our previous Suns, and this causes inconsistent behavior
! when that key is pressed in various windowmanagers.
keycode 233 = Meta_L
! As of Solaris 2.3, our good friends at Sun seem to have broken
! something in the parsing of /usr/openwin/share/etc/keytables so
! that only the first two entries on a modifier can work. This file
! should be removed as soon as it's no longer required.
add mod1 = Meta_L Multi_key
! One of the Meta_L keys works its way into mod4 as a result of the keycode
! line above, if we let it, and that prevents the windowmanager behavior we seek
clear mod4
