From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] The utility of a chording pad
Date: Sun, 5 Aug 2007 07:35:32 -0400 [thread overview]
Message-ID: <d97c9ebdbb1867951527be229975cf0e@quanstro.net> (raw)
> If I recall correctly Rob Pike's comments in this forum a long time
> ago apropos the issue of customisation, I would suggest that such a
> chording pad would be more frustrating than useful. It goes almost
> without saying that the generality of such a device lends itself to
> insane re-configuration by each user, with dramatic, if potentially
> humorous results.
i think it's hard to say without doing an experiment. there is no
reason one needs to use all the combinations. so it would be
interesting to add a forth button. perhaps one could disambiguate
between Look and Open. (how many times have you had to play
tricks because there is a symbol wumpus and file wumpus?)
> Consider that there are twelve function keys on the conventional
> keyboard and Plan 9 uses none of them. Nevermind the new keyboards
> with the full Jumbo Jet console on them.
that's because they're not standard. you can use them if you map them
with /dev/kbmap.
cpu% cat fkeys
0 59 '☺
0 60 '☹
☺ erik
next reply other threads:[~2007-08-05 11:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 11:35 erik quanstrom [this message]
2007-08-05 11:49 ` Lucio De Re
2007-08-05 11:59 ` Lucio De Re
2007-08-05 14:19 ` Steve Simon
2007-08-05 15:33 ` Lucio De Re
2007-08-05 15:33 ` Skip Tavakkolian
2007-11-06 21:26 ` maht-9fans
-- strict thread matches above, loose matches on Subject: below --
2007-08-05 3:50 john
2007-08-05 10:03 ` Lucio De Re
2007-08-05 15:53 ` Jack Johnson
2007-08-05 10:05 ` Gabriel Diaz
2007-11-06 21:49 ` Eric Van Hensbergen
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=d97c9ebdbb1867951527be229975cf0e@quanstro.net \
--to=quanstro@quanstro.net \
--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).