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 02:49:37 +0200	[thread overview]
Message-ID: <cok4lfypjy.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87ocarvxt8.fsf@windlord.stanford.edu> (Russ Allbery's message of "Mon, 18 Oct 2010 17:19:31 -0700")

Russ Allbery <rra@stanford.edu> writes:

> Richard Riley <rileyrg@googlemail.com> writes:
>
>> keyboard dependant I guess. $ is a shifted key for me and M-d seems
>> pretty instantaneous for someone using and familiar emacs.
>
> I don't believe it's keyboard-dependent, but I could be wrong.  I've never
> had meta survive ssh -> xterm -> emacs, which forces two keystrokes (ESC
> d) instead of one shifted keystroke.  It's quite a bit slower when marking
> multiple messages.

Maybe I'm missing something but M-<key> works fine. In this case M-d. M
not working would render emacs useless in a terminal I would have
thought. Possibly I get better results because its urxvt in tmux? I dont
recall M-d causing any issues in any other setups - I did have issues
with functions keys however! I tried getting me head around termcap etc
but, well, chickened out...

Still, if $ is popular then grand ;) I just wonder why set another key
where there is already another incumbent. Leave it to the individual.

Also the spam handling can be set for different marks on a per group
basis I believe. Not that I ever tried it.

,----
| [ ] Spam mark choices:
|     Set:
|     [ ] gnus-spam-mark
|                 Mark used for spam articles.
|     [ ] gnus-killed-mark
|                 Mark used for killed articles.
|     [ ] gnus-kill-file-mark
|                 Mark used for articles killed by kill files.
|     [ ] gnus-low-score-mark
|                 Mark used for articles with a low score.
|     Marks considered spam. [Hide Rest]    
|     Such articles will be processed as spam on group exit.  When nil, the global
|     spam-spam-marks variable takes precedence.
`----

So a kill could also result in spam processing.

best regards

r.




  reply	other threads:[~2010-10-19  0:49 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 [this message]
2010-10-19  1:05           ` Russ Allbery
2010-10-19  1:27             ` Richard Riley
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=cok4lfypjy.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).