From: Boyd Roberts <boyd@strakt.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] keyboard maps
Date: Tue, 21 May 2002 12:43:27 +0200 [thread overview]
Message-ID: <3CEA24CF.15A1DA79@strakt.com> (raw)
In-Reply-To: <1021751834.1076.18.camel@dator>
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.
next prev parent reply other threads:[~2002-05-21 10:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 17:37 Fco.J.Ballesteros
2002-05-15 9:05 ` Boyd Roberts
2002-05-15 21:34 ` Pavel Mihaylov
2002-05-16 10:02 ` Boyd Roberts
2002-05-18 19:57 ` Pavel Mihaylov
2002-05-21 10:43 ` Boyd Roberts [this message]
2002-05-21 11:35 ` Pavel Mihaylov
2002-05-14 18:50 andrey mirtchovski
2002-05-14 19:40 andrey mirtchovski
2002-05-14 20:15 rob pike, esq.
2002-05-14 21:36 rob pike, esq.
2002-05-16 10:00 Fco.J.Ballesteros
2002-05-16 11:06 nigel
2002-05-16 13:18 rob pike, esq.
2002-05-20 9:55 Joel Salomon
2002-05-21 8:47 ` Joel Salomon
2003-11-17 18:24 Fco.J.Ballesteros
2003-11-17 18:34 ` ron minnich
2003-11-17 18:41 ` Fco.J.Ballesteros
2003-11-17 19:56 ` mirtchov
2003-11-18 8:13 ` Fco.J.Ballesteros
2004-03-16 14:31 David Presotto
2005-11-01 21:48 Heiko Dudzus
2005-11-01 22:34 ` Russ Cox
2005-11-02 19:49 ` Heiko Dudzus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CEA24CF.15A1DA79@strakt.com \
--to=boyd@strakt.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).