Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Riley <rileyrg@googlemail.com>
To: Russ Allbery <rra@stanford.edu>
Cc: ding@gnus.org
Subject: Re: $ collision
Date: Tue, 19 Oct 2010 03:27:00 +0200	[thread overview]
Message-ID: <rk4ocjyntn.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87iq0zuh40.fsf@windlord.stanford.edu> (Russ Allbery's message of "Mon, 18 Oct 2010 18:05:35 -0700")

Russ Allbery <rra@stanford.edu> writes:

> Richard Riley <rileyrg@googlemail.com> writes:
>
>> Maybe I'm missing something but M-<key> works fine. In this case M-d.
>
> I promise, it doesn't me.  Apparently it works for you with the particular
> set of terminal emulators that you use, but it doesn't work for me running
> ssh inside a bog-standard xterm and never has in the fifteen plus years
> that I've been using Emacs.
>
>> M not working would render emacs useless in a terminal I would have
>> thought.
>
> That's why it's always been possible in Emacs to simulate meta by pressing
> ESC and then the character.

I guess this is where I am getting confused. Esc is the meta here or I
have certainly always thought of it as that .. but that to one side for
a moment : the rest of the emacs driving keys use M so do you redefine all
those or just use Esc as the Meta? Don't misunderstand me, I'm not
objecting per-se to anything I am just trying to understand why existing
keys that people use for Mairix are remapped to add a facility key to
something already mapped. I would have thought it fairly easy for
experienced emacs users to make their own convenient mappings when using
emacs hostile shells as you obviously are. I used emacs -nw for quite a
while but reverted to X in the end because it was so much easier to use
org mode and I had better abilities to remap Function and S/Function
keys and yes, I did experience different emacs "friendliness" depending
on which term I used.

regards

r.






  reply	other threads:[~2010-10-19  1:27 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-17 14:09 Lars Magne Ingebrigtsen
2010-10-17 21:32 ` Reiner Steib
2010-10-18 18:23   ` Lars Magne Ingebrigtsen
2010-10-19 14:15     ` Ted Zlatanov
2010-10-19 18:20       ` Lars Magne Ingebrigtsen
2010-10-18  7:33 ` Richard Riley
2010-10-18 16:27   ` Russ Allbery
2010-10-18 17:28     ` Richard Riley
2010-10-18 17:33       ` Adam Sjøgren
2010-10-19  0:19       ` Russ Allbery
2010-10-19  0:49         ` Richard Riley
2010-10-19  1:05           ` Russ Allbery
2010-10-19  1:27             ` Richard Riley [this message]
2010-10-19  1:32               ` Russ Allbery
2010-10-19 10:28                 ` Richard Riley
2010-10-19 16:12             ` James Cloos
2010-10-19 18:18               ` Lars Magne Ingebrigtsen
2010-10-19 18:40             ` Andreas Schwab
2010-10-19 10:34         ` Steinar Bang
2010-10-19 10:37           ` Steinar Bang
2010-10-19 10:53             ` Richard Riley
2010-10-20  2:54               ` Russ Allbery
2010-10-20  5:17                 ` Richard Riley
2010-10-20  8:28                   ` Adam Sjøgren
2010-10-19 17:04           ` Adam Sjøgren
2010-10-18 17:47 ` Ted Zlatanov
2010-10-18 18:14   ` Richard Riley
2010-10-18 18:55   ` David Engster

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=rk4ocjyntn.fsf@news.eternal-september.org \
    --to=rileyrg@googlemail.com \
    --cc=ding@gnus.org \
    --cc=rra@stanford.edu \
    /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 NNTP newsgroup(s).