emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Samuel Wales <samologist@gmail.com>
Cc: PT <spamfilteraccount@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: RSI
Date: Tue, 01 Sep 2009 15:50:08 -0400	[thread overview]
Message-ID: <87iqg2h2bz.fsf@fastmail.fm> (raw)
In-Reply-To: <20524da70909011111p2d990274l89722cae104b9722@mail.gmail.com> (Samuel Wales's message of "Tue, 1 Sep 2009 11:11:34 -0700")

Samuel Wales <samologist@gmail.com> writes:

> Repetitive strain injury is real and important.
>
> One thing that you can do is to ensure that you have a keyboard that
> has modifier keys on both sides.  You should pound a new habit into
> your cerebellum: use two hands.
>
> For example, c-c c-o should look like this:
>
>   r hand presses ctrl
>   l hand presses c
>   let go
>   l hand presses ctrl
>   r hand presses o
>   let go
>
> This is obviously inefficient, but it is the correct thing.
>
> Ideally, the most important c-c and c-x operations would be on the
> lhs.  That way, you can hold down ctrl and press the two keys.
>
> Many (maybe even most) will find this idea strange.  But I urge all of
> you to try it for a few months.

This is no doubt the correct method, but it is not realistic for many
users given the idiosyncratic layouts of keyboards today. Many of the
laptops I've used have had a misplaced or non-existent right control
key. Thus, short of using viper, the only solution that works for me is
to use the Caps Lock key as Control. With that slight modification, I
find emacs controls *very* comfortable (perhaps even as comfortable than
vim). Once I made that switch, RSI issues disappeared virtually
overnight.

Now, any RSI issues I experience come from using n and p or j and k
repeatedly.

Needless to say, YMMV.

Best,
Matt

  parent reply	other threads:[~2009-09-01 19:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-01 18:11 RSI Samuel Wales
2009-09-01 18:16 ` RSI Samuel Wales
2009-09-01 18:22 ` RSI Keith Lancaster
2009-11-04 11:22   ` RSI Adam Spiers
2009-11-04 14:30     ` RSI Bill Powell
2009-09-01 18:22 ` RSI PT
2009-09-01 19:50 ` Matt Lundin [this message]
2009-09-07  9:48   ` RSI Eric S Fraga, Eric S Fraga
2009-09-07 11:34     ` Alan E. Davis
2009-09-11 15:34     ` Matthew Lundin
2009-09-11 15:29       ` Eric S Fraga
2009-09-07 13:25 ` RSI B Smith-Mannschott
2009-09-07 17:16   ` RSI Daniel Martins
2009-09-07 19:48     ` RSI B Smith-Mannschott
2009-09-08  5:50     ` RSI PT
2009-09-08  8:05       ` RSI B Smith-Mannschott
     [not found] <4AAD12BA.90105@alumni.ethz.ch>
2009-09-13 17:03 ` RSI Michael Brand

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87iqg2h2bz.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@gmail.com \
    --cc=spamfilteraccount@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).