From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kbd.c
Date: Mon, 1 Apr 2002 18:33:08 +0200 [thread overview]
Message-ID: <20020401183307.E6290@cackle.proxima.alt.za> (raw)
In-Reply-To: <20020401162224.QANN443.mta4p@isabella>; from kazumi iwane on Tue, Apr 02, 2002 at 01:27:28AM +0900
On Tue, Apr 02, 2002 at 01:27:28AM +0900, kazumi iwane wrote:
>
> Using a special key sequence to modify the keyboard behavior
> itself smells a lot like emacs key binding madness.
>
One could declare a key, key combination or key sequence to be outside
the boundaries of key mapping, with an undo option, too.
> My vote goes to using a command whose name and arguments
> consist only of ASCII. It's only a mouse-click away in acme.
>
Not unreasonable.
My two cents' worth: what would we do if the keyboard was just another
RS-232 peripheral? Why not treat it as if? In the kernel one
converts all sorts of key madness to 256 (or even 65536) key codes
that can be looked up in a user-supplied UTF-8 lookup table. The
default can be altered in slices and restored with one command.
Am I missing something?
++L
next prev parent reply other threads:[~2002-04-01 16:33 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-30 21:28 rob pike, esq.
2002-03-30 22:41 ` Richard
2002-03-30 22:47 ` Digby Tarvin
2002-03-31 11:26 ` kazumi iwane
2002-03-31 12:21 ` kazumi iwane
2002-03-31 2:47 ` kazumi iwane
2002-03-31 18:32 ` George Bronnikov
2002-04-01 0:47 ` Boyd Roberts
2002-04-01 6:50 ` George Bronnikov
2002-04-01 7:22 ` Lucio De Re
2002-04-01 11:35 ` Boyd Roberts
2002-04-01 16:27 ` kazumi iwane
2002-04-01 16:33 ` Lucio De Re [this message]
2002-04-01 11:34 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2002-04-02 10:48 forsyth
2002-04-02 10:56 ` Lucio De Re
2002-04-02 10:42 forsyth
2002-04-08 12:54 ` Andries Brouwer
2002-04-02 9:31 forsyth
2002-04-02 9:44 ` Boyd Roberts
2002-04-02 8:28 Fco.J.Ballesteros
2002-04-02 8:17 Fco.J.Ballesteros
2002-04-02 5:04 plan9
2002-04-02 1:58 okamoto
2002-04-01 14:01 rob pike, esq.
2002-04-01 1:54 okamoto
2002-04-01 1:40 okamoto
2002-03-31 19:35 andrey mirtchovski
2002-03-31 14:48 bwc
2002-03-31 15:13 ` Boyd Roberts
2002-03-31 17:06 ` Digby Tarvin
2002-03-31 10:24 forsyth
2002-03-31 5:40 rob pike, esq.
2002-03-30 23:13 Russ Cox
2002-03-30 21:20 Geoff Collyer
2002-04-08 12:47 ` Matthew C Weigel
2002-03-30 21:10 rob pike, esq.
2002-03-30 21:08 rob pike, esq.
2002-03-31 18:58 ` FJ Ballesteros
2002-04-01 0:36 ` Boyd Roberts
2002-04-01 0:42 ` Boyd Roberts
2002-03-23 12:01 George Bronnikov
2002-03-30 21:05 ` FJ Ballesteros
2002-03-31 12:45 ` Boyd Roberts
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=20020401183307.E6290@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).