From: "Robert J. Chassell" <bob@rattlesnake.com>
Cc: emacs-devel@gnu.org
Subject: Re: German tutorial fix
Date: Thu, 23 May 2002 19:45:05 +0000 (UTC) [thread overview]
Message-ID: <m17AyWH-000If2C@localhost> (raw)
In-Reply-To: <87elg8upk7.fsf@emacswiki.org> (message from Alex Schroeder on Sun, 19 May 2002 17:26:16 +0200)
Miles Bader <miles@gnu.org> writes:
> It's easily observable by any touch-typist, by (1) taking some time to
> get used to the control-keys, and (2) trying both for about 3 seconds
> while typing in some text. It's not a subtle thing.
I do not find it easily observable. I bet it also depends on keyboard
layout and customizations outside of Emacs.
Do please tell me your keyboard and customizations.
I just tried Miles' experiment on a QWERTY keyboard, with the arrow
keys to the lower right. By counting how many I could press in 5 and
10 seconds, I found that I can press C-n or C-p in 200 milliseconds or
so and press an arrow key in 800 milliseconds or so. (Presumably,
with more practice, I could speed up my arrow key press time, but
still, that action has to take longer than pressing a control key
since it requires moving my right hand two rows down and 3.5 rows to
the right but pressing a control-chord does not require moving my
hands, just my fingers.)
As far as I can see, the arrow keys are as Miles says, *more obvious*.
But in my experience, on the computer keyboards I have been using for
the past generation, they are less efficient than control keys.
--
Robert J. Chassell bob@rattlesnake.com
Rattlesnake Enterprises http://www.rattlesnake.com
next prev parent reply other threads:[~2002-05-23 19:45 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 13:07 German tutorial fix Mario Lang
2002-05-14 15:05 ` Kai Großjohann
2002-05-16 7:22 ` Richard Stallman
2002-05-16 10:37 ` Kai Großjohann
2002-05-16 12:52 ` Eli Zaretskii
2002-05-16 14:10 ` Andreas Fuchs
2002-05-16 15:37 ` Eli Zaretskii
2002-05-17 19:28 ` Richard Stallman
2002-05-18 0:44 ` Francesco Potorti`
2002-05-18 2:00 ` Miles Bader
2002-05-18 7:17 ` Andreas Fuchs
2002-05-18 11:59 ` Francesco Potorti`
2002-05-18 12:12 ` Miles Bader
2002-05-18 12:55 ` Eli Zaretskii
2002-05-18 13:11 ` Andreas Fuchs
2002-05-19 4:56 ` Eli Zaretskii
2002-05-19 5:30 ` Richard Stallman
2002-05-18 20:36 ` Kim F. Storm
2002-05-20 22:58 ` Francesco Potorti`
2002-05-19 5:30 ` Richard Stallman
2002-05-19 12:54 ` Alex Schroeder
2002-05-19 13:30 ` Miles Bader
2002-05-19 14:47 ` Stefan Monnier
2002-05-19 15:26 ` Alex Schroeder
2002-05-19 16:10 ` Miles Bader
2002-05-20 10:47 ` Alex Schroeder
2002-05-23 19:45 ` Robert J. Chassell [this message]
2002-05-23 23:45 ` Alex Schroeder
2002-05-20 14:48 ` Richard Stallman
2002-05-18 14:18 ` Alex Schroeder
2002-05-18 6:44 ` Eli Zaretskii
2002-05-19 19:44 ` Robert J. Chassell
2002-05-20 14:40 ` Mario Lang
2002-05-20 21:13 ` Colin Walters
2002-05-17 19:28 ` Richard Stallman
2002-05-15 0:13 ` Werner LEMBERG
2002-05-15 4:41 ` Eli Zaretskii
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=m17AyWH-000If2C@localhost \
--to=bob@rattlesnake.com \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.