From: Eric Abrahamsen <girzel@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Arrow Keys?
Date: Mon, 8 Jun 2009 00:27:26 +0800 [thread overview]
Message-ID: <DCF82835-64D4-44DA-9682-F3020F9E2EAB@gmail.com> (raw)
In-Reply-To: <e01d8a50906070458r606a56feqf73d128a7d03debc@mail.gmail.com>
On Jun 7, 2009, at 7:58 PM, Lennart Borgman wrote:
> On Sun, Jun 7, 2009 at 1:02 PM, Christian
> Herenz<herenz@physik.hu-berlin.de> wrote:
>> Chris Gordon-Smith schrieb:
>>>
>>> Hello All
>>>
>>> I have recently started using Emacs on a regular basis. I read in
>>> the
>>> Emacs documentation that it is more efficient to use C-N, C-P etc.
>>> rather
>>> than arrow keys. Is this really true? I'm persisting with it, but
>>> those
>>> arrow keys still seem pretty attractive.
I've been using emacs for less than a year. I feel comfortable with
python mode, outline mode, dired, org-mode, slime and auctex. And yet,
the stupid f-b-n-p issue is a constant pain. Why, in an editor that's
utilized through habit and muscle memory, are the most primary
navigation keys based on *mnemonic* devices like forward-back-next-
previous? Why is that necessary? I can open files on remote servers,
eval defuns, and relocate sub-trees easier than I can move forward
three words and then move forward another two characters. I'm aware of
solutions like ergo-movement or whatever, but it messes with the whole
arrangement of keys and really isn't viable. Only now, after nearly a
year of use, am I finally getting to the point where it is more
efficient to reach for f-b-n-p than to reach for the arrow keys.
This is a rant. I have no real point. In the end, it's better to use f-
b-n-p, but good Lord it takes a long time to get here.
E
>>
>> Yeah... I also tend to use them frequently for navigational
>> purposes. But, I
>> think the general idea is, that you dont have to move the hand away
>> from the
>> area which it is on, when you are writing.
>
> ... and you can of course use Emacs with a vi key interface (Viper)
> which is (according to some people) more efficient ... once you have
> learned it of course ... ;-)
>
>
next prev parent reply other threads:[~2009-06-07 16:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-07 10:41 Arrow Keys? Chris Gordon-Smith
2009-06-07 11:02 ` Christian Herenz
2009-06-07 11:58 ` Lennart Borgman
2009-06-07 16:27 ` Eric Abrahamsen [this message]
[not found] ` <mailman.162.1244392060.2239.help-gnu-emacs@gnu.org>
2009-06-07 17:05 ` Xah Lee
2009-06-07 21:24 ` notbob
2009-06-08 5:13 ` Eric Abrahamsen
2009-06-08 11:46 ` Teemu Likonen
2009-06-12 17:34 ` John A Pershing Jr
2009-06-12 18:38 ` Teemu Likonen
2009-06-12 20:57 ` Jeff Clough
[not found] ` <mailman.556.1244868430.2239.help-gnu-emacs@gnu.org>
2009-06-13 15:45 ` notbob
2009-06-13 16:12 ` Teemu Likonen
2009-06-07 21:31 ` Chris F.A. Johnson
2009-06-07 22:18 ` Chris Gordon-Smith
2009-06-08 4:58 ` Ian Eure
2009-06-07 22:55 ` Davin Pearson
2009-06-08 0:38 ` Eli Zaretskii
2009-06-13 17:13 ` Andreas Röhler
[not found] ` <mailman.569.1244913073.2239.help-gnu-emacs@gnu.org>
2009-06-13 18:08 ` B. T. Raven
[not found] ` <mailman.179.1244421488.2239.help-gnu-emacs@gnu.org>
2009-06-08 20:05 ` Chris Gordon-Smith
2009-06-21 12:01 ` Chris Gordon-Smith
2009-07-06 0:16 ` Miles Bader
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=DCF82835-64D4-44DA-9682-F3020F9E2EAB@gmail.com \
--to=girzel@gmail.com \
--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).