unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Xah Lee <xah@xahlee.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs key bindings through the ages
Date: Thu, 15 Nov 2007 00:33:52 -0800 (PST)	[thread overview]
Message-ID: <df9eade0-b760-4c93-9717-8b7b9e70ff30@d21g2000prf.googlegroups.com> (raw)
In-Reply-To: 1195020235.983333.46390@o38g2000hse.googlegroups.com

emacs's keybind is actually the worst possible in both ergonomic and
ease of use considerations. Likely a randomly generated shortcut set
will have a 30% chance better.

See: Why Emacs's Keyboard Shortcuts Are Painful
http://xahlee.org/emacs/emacs_kb_shortcuts_pain.html

The Modernization of Emacs
http://xahlee.org/emacs/modernization.html

  Xah
  xah@xahlee.org
\xAD\xF4 http://xahlee.org/

On Nov 13, 10:03 pm, bramble <cadet.bram...@gmail.com> wrote:
The default GNU Emacs key bindings seem to work very well. They seem
particularly well-thought-out, in fact. Like stones in a stream, worn
by movement and time to have very few rough edges... They mesh well
with the ascii control characters, and I particularly like how M-<foo>
is often used as a sort of "turbo boost" to C-<foo> (like C-f vs. M-f,
for example). In cases where it makes no sense to boost the C-key,
Emacs often has elegant mnemonic bindings, for example, M-u, M-l, M-c.

Were the bindings designed as such right from the beginning by only
RMS? Or have they morphed over the years, with user and developer
requests guiding changes? Can anyone shed any light on the history of
the default key binding choices?

(Please note, I don't wish to start another thread comparing Emacs key
combinations with CUA bindings. I realize that, for whatever reasons,
some people just don't like or can't get used to Emacs key combos, but
I was hoping this thread would simply address the development and
history of Emacs bindings over time.)

Thanks.

  parent reply	other threads:[~2007-11-15  8:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-14  6:03 Emacs key bindings through the ages bramble
2007-11-14 16:07 ` Stefan Monnier
2007-11-14 16:27   ` rustom
2007-11-14 17:05   ` Juanma Barranquero
     [not found]   ` <mailman.3533.1195059944.18990.help-gnu-emacs@gnu.org>
2007-11-15 10:49     ` Stefan Kamphausen
2007-11-15 18:47       ` Amy Templeton
2007-11-15 21:33       ` bramble
2007-11-16  5:23         ` Tim X
2007-11-16 12:26         ` rustom
2007-11-16 15:45           ` Lennart Borgman (gmail)
     [not found]           ` <mailman.3662.1195227958.18990.help-gnu-emacs@gnu.org>
2007-11-16 16:45             ` rustom
2007-11-16 17:48               ` Lennart Borgman (gmail)
2007-11-18  4:50           ` Stefan Monnier
2007-11-18  8:47             ` rustom
2007-11-15  1:16 ` Barry Margolin
2007-11-15  3:19   ` bramble
2007-11-15  8:33 ` Xah Lee [this message]
2007-11-15 14:06   ` Lennart Borgman (gmail)
     [not found]   ` <mailman.3592.1195135588.18990.help-gnu-emacs@gnu.org>
2007-11-15 16:01     ` rustom

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=df9eade0-b760-4c93-9717-8b7b9e70ff30@d21g2000prf.googlegroups.com \
    --to=xah@xahlee.org \
    --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).