From: serge@euler.Berkeley.EDU serge@euler.Berkeley.EDU
Subject: plan 9 licenses
Date: Tue, 11 Apr 1995 03:16:24 -0400 [thread overview]
Message-ID: <19950411071624.qDhu6KiMogEWd9fhgBC7KWeb5GBtiSWG6TXJrd2324U@z> (raw)
>>If I (as a hypothetical example) add keyboard accelerators to Acme,
>150 hours of community service for that one, i think.
I'm not so sure about this. A mouse is nice, true, but it takes time to get
your hands from the keyboard to the mouse and back again (especially back
again, since you have to reposition them, e.g. if you're a touch typist).
Until we have better/more integrated keyboard/mouse input devices (e.g. on
one of the PC shows I saw a keyboard split in two, with each half acting as a
mouse by you just moving it around with [roughly] the palm of your hand), I
think the keyboard will remain very valuable. For example, (one of the reasons
:-) I don't like Netscape is that it doesn't have easy keyboard shortcuts.
What do people (especially Plan9 ones :-) think?
next reply other threads:[~1995-04-11 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-04-11 7:16 serge [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-04-11 10:44 arnold
1995-04-10 8:00 forsyth
1995-04-09 21:33 arnold
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=19950411071624.qDhu6KiMogEWd9fhgBC7KWeb5GBtiSWG6TXJrd2324U@z \
--to=serge@euler.berkeley.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).