From: steve.simon@snellwilcox.com
To: 9fans@cse.psu.edu
Subject: Re[2]: [9fans] Re: Keyboard mapping
Date: Fri, 6 Apr 2001 11:20:04 +0100 [thread overview]
Message-ID: <402492341@snellwilcox.com> (raw)
Hi,
On the serious note of copeing with RSI: Raising
my monitor and chair by 6 inches, and finding a mouse
with buttons that require only a light pressure but
then move a significant amount helped me a great deal.
-Steve
____________________Reply Separator____________________
[snip]
the acme-style mouse chording...
what concerns me about the chord interface is that the stress issue
is overlooked. i avoid chord-related RSI by carefully avoiding too much
chording on wily. that slows me down, but avoids a much worse situation.
[i gave up emacs years ago because of left-hand control-stress.]
i also wanted to say earlier that sam is fine the way it is. its
popup menu is nearly as fast as chords, and does not appear to
induce stress.
[snip]
next reply other threads:[~2001-04-06 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-06 10:20 steve.simon [this message]
2001-08-26 9:28 geoff
2001-08-26 12:50 ` Boyd Roberts
2001-08-27 11:18 ` Re[2]: " Matt
2001-08-27 11:24 ` 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=402492341@snellwilcox.com \
--to=steve.simon@snellwilcox.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).