Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: can gnus-unread-mark be a ham mark?
Date: Fri, 31 Oct 2003 12:52:32 -0500	[thread overview]
Message-ID: <4n1xst8fbz.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <76n0bhxqbs.fsf@newjersey.ppllc.com> (Jake Colman's message of "Fri, 31 Oct 2003 12:35:51 -0500")

On Fri, 31 Oct 2003, colman@ppllc.com wrote:

>>>>>> "BW" == Bill White <billw@wolfram.com> writes:
> 
>    BW> On Fri Oct 31 2003 at 10:47, Ted Zlatanov <tzz@lifelogs.com>
>    BW> said:
>    >> That way, I go into my spam group, mark ham with `!', and just
>    >> exit the group.
> 
>    BW> [...]
> 
>    >> The ham-marked articles, namely the ticked ones, get moved to
>    >> "mail" and *unmarked* (this is the part I think you want), so
>    >> they look fresh and new.  I don't use a ham-exit-processor on
>    >> them currently.
> 
>    BW> Excellent - this is working for me now, and ticked makes even
>    BW> more sense to me than unmarked.  Thanks!
> 
> You could also have used the gnus-del-mark ('r') for the same thing,
> right?

Any ham-mark, really, will work.

Ted



  reply	other threads:[~2003-10-31 17:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-30  1:50 spam/ham processing Jake Colman
2003-10-30 15:33 ` Ted Zlatanov
2003-10-30 17:13   ` Jake Colman
2003-10-31 14:00   ` can gnus-unread-mark be a ham mark? Bill White
2003-10-31 16:47     ` Ted Zlatanov
2003-10-31 17:09       ` Bill White
2003-10-31 17:35         ` Jake Colman
2003-10-31 17:52           ` Ted Zlatanov [this message]
2003-10-31 17:53           ` Bill White

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=4n1xst8fbz.fsf@lockgroove.bwh.harvard.edu \
    --to=tzz@lifelogs.com \
    --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).