From: B Smith-Mannschott <bsmith.occs@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Re: RSI
Date: Tue, 8 Sep 2009 10:05:51 +0200 [thread overview]
Message-ID: <28c656e20909080105g4355dd83vccf29d8a7d52fe83@mail.gmail.com> (raw)
In-Reply-To: <loom.20090908T074857-149@post.gmane.org>
On Tue, Sep 8, 2009 at 07:50, PT<spamfilteraccount@gmail.com> wrote:
> Daniel Martins <danielemc <at> gmail.com> writes:
>
>> Sticky keys takes some getting used to. It makes every modifier key
>> work a little like caps lock. Sounds horrible, doesn't it? Well, it's
>> not really. Basically, if you press control once, it "locks" control
>> down for the next keystroke only, after which point the keyboard
>> returns to normal. Press control twice, and it locks down until you
>> release it with a third press.
>> C-x C-f
>> Used to be: press and hold control. Press and release x. press and
>> release f. Release control.
>> Now it's Press and release control twice. Press and release x. press
>> and release f. Press and release control.
>
> I don't know which implementation you use, but with Windows' built-in
> sticky key setup there is no change compared to the usual order of keys:
>
>
> press/release ctrl, press/release x, press/release ctrl, press/release f
>
> No need to press and release control twice at the beginning, so it's the
> same number of keypresses as the usual method, you only need to pay
> attention you release the previous key before pressing the next one.
yes, you can do it this way too, in fact I usually do for two-key
sequences. You do have the option of "locking down" a modifier key by
pressing it twice. Press once more to release it. Occasionally I find
myself inputting a burst of keystrokes under the same modifier, in
cases like that it can make sense to do this. (Think of it as a
"mode", in the way that word is used among the vi crowd.) I use that
when I'm going to be repeating the same control key binding often,
i.e. when I'm isearching through a document looking at all the
matches:
[ctrl] [s] sometext [ctrl][ctrl] [s] [s] [s] [s] [s] [s] [s] ... [ctrl]
instead of
[ctrl] [s] sometext [ctrl] [s] [ctrl] [s] [ctrl] [s] [ctrl] [ctrl] [s]
[ctrl] [s] [ctrl] [s] [ctrl] [s] ...
// Ben
next prev parent reply other threads:[~2009-09-08 8:06 UTC|newest]
Thread overview: 20+ 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 ` RSI Matt Lundin
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 ` B Smith-Mannschott [this message]
[not found] <4AAD12BA.90105@alumni.ethz.ch>
2009-09-13 17:03 ` RSI Michael Brand
2009-09-13 20:42 ` RSI Dave Täht
2009-09-14 9:06 ` Eric S Fraga, Eric S Fraga
2009-09-15 0:56 ` Dave Täht
2009-09-15 9:20 ` Eric S Fraga
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=28c656e20909080105g4355dd83vccf29d8a7d52fe83@mail.gmail.com \
--to=bsmith.occs@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).