all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John A Pershing Jr <pershing@alum.mit.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: Arrow Keys?
Date: Fri, 12 Jun 2009 13:34:17 -0400	[thread overview]
Message-ID: <uhbyl5pba.fsf@alum.mit.edu> (raw)
In-Reply-To: mailman.162.1244392060.2239.help-gnu-emacs@gnu.org

Eric Abrahamsen <girzel@gmail.com> writes:

> 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 don't understand what the problem is, here.  The arrow keys work just
fine, for those of you who don't/can't touch type.  The mouse works just
fine, too.  And, the control-meta-cokebottle keys work just fine for
those of us who *do* touch type.  If you don't like C-f, then don't use
it.  It's as simple as that.

Or, are you saying that you hit these keys by accident?  If so, then
undefine them in your .emacs file.

Now, for the "why":  Emacs is an old editor.  *Very* old.  Dating back
nearly 40 years, when it was implemented as the world's largest TECO
macro, and ran on a DEC-10 mainframe.  Many terminals didn't have arrow
keys, and those that did encoded them (in ASCII) in vendor-unique ways.
The only thing that was known to work were the standard (7-bit) ASCII
characters, with ESC used to add in the META bit.  (I didn't have access
to any of the Knight terminals, which transmitted 12(?)-bit characters,
including a real META bit).  If you had, say, a DEC VT-100 terminal,
then you had to load up the VT100 macro package for the arrow keys to be
recognized.  Most of us simply didn't bother.  Hence, C-f, C-b, C-p, and
C-n.

However, I admit that some of the mnemonics are a bit of a stretch...

  -jp


  parent reply	other threads:[~2009-06-12 17:34 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
     [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 [this message]
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

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

  git send-email \
    --in-reply-to=uhbyl5pba.fsf@alum.mit.edu \
    --to=pershing@alum.mit.edu \
    --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.
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.