Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!ncar!tank!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.ultrix
Subject: Re: Meta (Compose) Key Strangeness on DS3100
Keywords: Digital DS3100 Xterm Meta Wierd UWS 2.0
Message-ID: <19308@mimsy.UUCP>
Date: 29 Aug 89 06:01:24 GMT
References: <865@hadron.UUCP> <19274@mimsy.UUCP> <8360@boring.cwi.nl>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 27

>chris@mimsy.UUCP (Chris Torek) writes:
>[some hints about making the LK201 keyboard tolerable]
>>I would still pay good money for a keyboard that does not make my
>>left pinky ache.

In article <8360@boring.cwi.nl> guido@piring.cwi.nl (Guido van Rossum) writes:
>You disabled the Lock key, but went only halfway.  It can become a
>Control key ....

The control key is not the major cause of `sore finger syndrome'.  It
is that !#*()% `<>' key between Z and SHIFT.

Now, if I could make <> act like SHIFT. . . .  The MIT xmodmap manual
seems to imply that

	xmodmap -e 'keycode 201 = Shift_L'
	xmodmap -e 'add Shift = Shift_L'

should work, but it fails silently (the <> key does nothing at all).
Changing both Shift_Ls to Shift_Rs causes the following error:

	[gyre122] xmodmap -e 'keycode 201 = Shift_R'
	[gyre123] xmodmap -e 'add shift = Shift_R'
	xmodmap: bad set modifier mapping.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris