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

Richard Riley <rileyrg@googlemail.com> writes:

> 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?

I use ESC as meta, but most meta sequences in Emacs don't have to be
repeated multiple times.  The only other one I ever remember noticing this
with is M-v, and I don't use that anywhere near as much as marking
messages as spam.  In order to have M-d be a single shifted keystroke,
there has to be a shift key on the keyboard that can successfully act as
the meta shift key (not the ESC prefix workaround), which is true in X but
not (for me at least) in an xterm through ssh to emacs -nw on the other
side.

If one is marking multiple messages as spam, it's much more annoying to
have to alternate between two keys (and ESC is often in an awkward
location) than to just repeatedly use the same key, possibly shifted.

> 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've never even heard if nnmairix before the last month and certainly
wasn't aware of it when I proposed the additional key binding, and I
suspect Lars wasn't aware either.

I don't use it and therefore don't particularly care; I can continue to
locally map $ to the right thing since I don't use nnmairix.  But it
seemed like it would make mark handling more consistent.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>



  reply	other threads:[~2010-10-19  1:32 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
2010-10-19  1:32               ` Russ Allbery [this message]
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=87eibnufuq.fsf@windlord.stanford.edu \
    --to=rra@stanford.edu \
    --cc=ding@gnus.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 NNTP newsgroup(s).