From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: How to bind isearch-repeat-forward to F3 in a certain mode only?
Date: Thu, 30 Jul 2015 05:15:15 +0200 [thread overview]
Message-ID: <87si86z67w.fsf@nl106-137-147.student.uu.se> (raw)
In-Reply-To: 20150730010304.18190.1F77C36E@ahiker.mooo.com
Ian Zimmerman <itz@buug.org> writes:
> Key combinations involving a modifier (sometimes
> called "chords") are appreciably harder to perform,
> and more likely to lead to RSI, than sequences of
> single keystrokes.
Not necessarily! It all depends.
For example, I have M-o to do
(defun other-window-or-split ()
(interactive)
(when (= 1 (count-windows)) (split-window-vertically))
(other-window 1) )
which I do all the time. If you put your fingers into
proper positions - real hackers don't have to do this,
because they always have them there anyway - and look
down, observe what minimal motion of the left thumb,
and right ring finger, in order to hit this shortcut,
and the *zero* hand motion.
Compared to some single keys - in particular:
a s d f j k l ;
then yes, M-o is barely slower and less ergonomic, but
compared to many, many single keys M-o is much better.
And I don't only mean the F* keys; the numeric keypad;
the arrow keys; the Home, End, etc. keys; and all that
which are obviously incomparably worse to fingers,
hands, neck, and eyes. No, M-o is also better than the
digit keys, most keys below your left hand (i.e., z,
x, c, with the exception of v which is comparable to
M-o); and so on.
So if those prefix keys are placed wisely, they
shouldn't be thought of as unergonomic.
This file contains a lot, but if you search for
"prefix" you see how a new one can be setup easily and
thereafter used like the standard ones.
http://user.it.uu.se/~embe8573/conf/emacs-init/global-keys.el
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2015-07-30 3:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 22:01 How to bind isearch-repeat-forward to F3 in a certain mode only? Marcin Borkowski
2015-07-24 12:53 ` Michael Heerdegen
2015-07-27 21:13 ` Marcin Borkowski
2015-07-27 21:43 ` Michael Heerdegen
2015-07-27 23:45 ` Emanuel Berg
2015-07-28 0:26 ` Ian Zimmerman
2015-07-28 1:07 ` Emanuel Berg
2015-07-28 8:30 ` Marcin Borkowski
2015-07-28 16:15 ` Yuri Khan
[not found] ` <mailman.7513.1438072243.904.help-gnu-emacs@gnu.org>
2015-07-28 8:42 ` Rusi
2015-07-28 8:50 ` Marcin Borkowski
2015-07-28 15:01 ` Ian Zimmerman
2015-07-28 15:28 ` Marcin Borkowski
[not found] ` <mailman.7552.1438097346.904.help-gnu-emacs@gnu.org>
2015-07-30 0:23 ` Hikaru Ichijyo
2015-07-30 1:17 ` Ian Zimmerman
2015-07-30 3:15 ` Emanuel Berg [this message]
2015-07-30 5:10 ` Ian Zimmerman
2015-07-30 22:36 ` Emanuel Berg
[not found] ` <mailman.7637.1438219082.904.help-gnu-emacs@gnu.org>
2015-07-30 1:48 ` Hikaru Ichijyo
2015-07-30 12:56 ` HASM
2015-07-30 22:37 ` Emanuel Berg
[not found] ` <mailman.7551.1438095703.904.help-gnu-emacs@gnu.org>
2015-07-28 17:00 ` Rusi
2015-07-28 1:02 ` Marcin Borkowski
[not found] <mailman.7323.1437688903.904.help-gnu-emacs@gnu.org>
2015-07-23 22:53 ` Javier
2015-07-23 23:09 ` Marcin Borkowski
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87si86z67w.fsf@nl106-137-147.student.uu.se \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@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.
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).