all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Teemu Likonen <tlikonen@iki.fi>
To: Silvio Levy <levy@msri.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: M-x mystery
Date: Mon, 02 Jan 2012 21:40:57 +0200	[thread overview]
Message-ID: <87y5tp6gfq.fsf@mithlond.arda> (raw)
In-Reply-To: <20120102173715.D8C94180B85@neo.msri.org> (Silvio Levy's message of "Mon, 02 Jan 2012 09:37:15 -0800")

* 2012-01-02T09:37:15-08:00 * Silvio Levy wrote:

> And that's what I don't understand. It's one thing for <ESC> x to be
> treated as M-x because some people lack that alt key, but for emacs to
> *convert* the keycode <alt>x to <ESC> x seems to me like poor design.

That's a historical Unix text terminal thing. All input must have a
"slot" in the current character set. That is, everything must be a
character (code). There is this concept of Meta key which is produced by
Esc in today's keyboards. Its Ascii code is 27 so it's a character (kind
of).

If we want to use Alt key in text terminals we must decide which
character (code) it produces. Well, the choice has already been made for
us. Alt+x was chosen to insert Meta x so that it's easier to type those
Meta key combinations.

Emacs in Unix text terminals is tied to this design of text terminals
(remember, you can use them through a modem/serial line). Emacs's
graphical user interface does not _need_ to be as limited but apparently
developers want it to be as compatible as possible anyway - and I agree
with them.



  parent reply	other threads:[~2012-01-02 19:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-02 17:37 M-x mystery Silvio Levy
2012-01-02 18:26 ` Drew Adams
2012-01-02 19:40 ` Teemu Likonen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-01-02 22:33 Silvio Levy
2012-01-02 23:25 ` Drew Adams
2012-01-02 20:07 Silvio Levy
2012-01-02  9:51 Silvio Levy
2012-01-02 16:32 ` Alexander
2012-01-02 16:34 ` Drew Adams

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=87y5tp6gfq.fsf@mithlond.arda \
    --to=tlikonen@iki.fi \
    --cc=help-gnu-emacs@gnu.org \
    --cc=levy@msri.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.