From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3CEA24CF.15A1DA79@strakt.com> From: Boyd Roberts MIME-Version: 1.0 To: 9fans@cse.psu.edu Subject: Re: [9fans] keyboard maps References: <2ddd507ce00ca87c2bcc7eb42e70c919@plan9.escet.urjc.es> <1021498469.3079.20.camel@dator> <3CE383A5.F60D645B@strakt.com> <1021751834.1076.18.camel@dator> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 21 May 2002 12:43:27 +0200 Topicbox-Message-UUID: 98906e40-eaca-11e9-9e20-41e7f4b1d025 Pavel Mihaylov wrote: > I'm changing it back to 0x80 since key View (Down) is defined as > Spec|0x00. The value 0x80 for View is hardcoded in rio, acme and sam and > when redefined those programs no longer recognise View as a special key, > and just insert it as text. Are you sure you've taken into account that kbtab and kbtabesc1 map the scan codes into Runes? In View's case it should just be defined as 0x80. It gets that value as a side effect of the value of Spec. Admittedly I overlooked this case, but I never type View anyway. > According to Unicode characters 0x0080 to > 0x009F are designated as control ones so it is safe to use them for > special keys. I don't think the following would agree: http://www.unicode.org/charts/PDF/U0080.pdf They may be well control values but some of them have a defined meaning.