From mboxrd@z Thu Jan  1 00:00:00 1970
Subject: Re: [9fans] keyboard maps
From: Pavel Mihaylov <bin@bash.info>
To: 9fans@cse.psu.edu
In-Reply-To: <3CEA24CF.15A1DA79@strakt.com>
References: <2ddd507ce00ca87c2bcc7eb42e70c919@plan9.escet.urjc.es>
	<1021498469.3079.20.camel@dator>  <3CE383A5.F60D645B@strakt.com>
	<1021751834.1076.18.camel@dator>  <3CEA24CF.15A1DA79@strakt.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <1021980904.2643.41.camel@eniac>
Mime-Version: 1.0
Date: Tue, 21 May 2002 14:35:03 +0300
Topicbox-Message-UUID: 9894e4b6-eaca-11e9-9e20-41e7f4b1d025

=D0=9D=D0=B0 21 =D0=BC=D0=B0=D0=B9 2002 =D0=B3. (=D0=B2=D1=82=D0=BE=D1=80=
=D0=BD=D0=B8=D0=BA), =D0=B2 13.43 =D1=87=D0=B0=D1=81=D0=B0, Boyd Roberts =
=D0=BF=D0=B8=D1=81=D0=B0:
> 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 an=
d
> > when redefined those programs no longer recognise View as a special key=
,
> > and just insert it as text.
>=20
> 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.
>=20
Scan codes are irrelevant here. Interaction with all those key
definitions takes place _after_ scan codes were mapped to runes. And
even the special keys are defined as normal runes in the tables.

> Admittedly I overlooked this case, but I never type View anyway.
>=20
> > According to Unicode characters 0x0080 to
> > 0x009F are designated as control ones so it is safe to use them for
> > special keys.
>=20
> I don't think the following would agree:
>=20
>     http://www.unicode.org/charts/PDF/U0080.pdf
>=20
> They may be well control values but some of them have a defined meaning.
>=20
Yes, that is correct. But as I said only Break leaves the kernel, and
possibly PF and Middle in future keymaps. For those keys we can possibly
choose other values from the U0080 control range (there are several
"just control" characters and two "private use" ones without predefined
meaning). The other Spec keys can be assigned arbitrary Unicode value
which is not intended to be typed as a normal character and not used in
Plan 9 as a control one. IMO, using the first characters in U0080 is OK
for all Spec keys as those "predefined control meanings" do control
nothing in Plan 9.

Regards,
Pavel