From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Foreign keyboard layout
Date: Wed, 26 Sep 2001 21:05:29 -0400 [thread overview]
Message-ID: <20010927010531.CDC87199E4@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 236 bytes --]
hence the comment in kbd.c:
KF= 0xF000, /* function key (begin Unicode private space) */
my comment was more that looking at the code
i think nothing really depends on Spec being 0x80
and it could just as easily be 0xF000.
[-- Attachment #2: Type: message/rfc822, Size: 1884 bytes --]
From: "Boyd Roberts" <boyd@fr.inter.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Foreign keyboard layout
Date: Thu, 27 Sep 2001 00:58:41 +0200
Message-ID: <01a401c146de$c989f470$a2b9c6d4@SOMA>
> i think you can safely ,s/Spec/KF/g and the
> keyboard driver will still work, without
> any 0x80 bits.
brucee tells me:
# Runes for special purposes (0xe800-0xfdff is Private Use Area)
next reply other threads:[~2001-09-27 1:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 1:05 Russ Cox [this message]
2001-09-27 1:06 ` Boyd Roberts
2001-09-29 2:44 ` Boyd Roberts
2001-09-29 20:49 ` Boyd Roberts
2001-09-30 2:20 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2001-09-26 22:45 Russ Cox
2001-09-26 22:48 ` Boyd Roberts
2001-09-26 22:58 ` Boyd Roberts
2001-09-26 22:10 forsyth
2001-09-26 17:08 rog
2001-09-26 17:07 ` Boyd Roberts
2001-09-26 21:43 ` Boyd Roberts
2001-09-24 17:47 forsyth
2001-09-24 17:56 ` Boyd Roberts
2001-09-24 16:58 forsyth
2001-09-24 17:21 ` Boyd Roberts
2001-09-26 16:41 ` Boyd Roberts
2001-09-18 7:02 Jesus A. Mora
2001-09-18 10:51 ` Boyd Roberts
2001-09-19 10:52 ` Jesus A. Mora
2001-09-19 12:49 ` Boyd Roberts
2001-09-19 16:52 ` Quinn Dunkan
2001-09-19 17:07 ` Boyd Roberts
2001-09-20 7:43 ` Jesus A. Mora
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=20010927010531.CDC87199E4@mail.cse.psu.edu \
--to=rsc@plan9.bell-labs.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).