Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: What's wrong with my spam.el settings now?
Date: 4 Oct 2005 14:04:40 -0400	[thread overview]
Message-ID: <4n64sdjgzr.fsf@lifelogs.com> (raw)
In-Reply-To: <iluoe6bif23.fsf@latte.josefsson.org> (Simon Josefsson's message of "Fri, 30 Sep 2005 02:18:12 +0200")

On Fri, 30 Sep 2005, jas@extundo.com wrote:

> This information and the information earlier in the thread doesn't add
> up for me.  Earlier I interpreted the problem that seen marks were
> visible on articles the second time you entered a group with that
> article.  Did I misunderstand that?  Is that still the problem?  If
> the seen list is updated as above, then the summary buffer shouldn't
> have a "unseen" mark on the 11844 article upon entering the group the
> second time.  Did it?
> 
> I'm not sure how this problem relate to the spam mark, but presumably
> it is because spam.el use the seen mark to decide which articles to
> mark as spam?

In spam groups, spam.el will spam-mark unseen articles only (unless
spam-mark-only-unseen-as-spam is nil, which does not apply here
because Bjorn reports the unseen mark is returning).  So the problem
seems to be the unseen mark's return, not the spam.el code.

Ted



      parent reply	other threads:[~2005-10-04 18:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07  6:38 Björn Lindström
2005-09-20 16:07 ` Ted Zlatanov
2005-09-20 17:10   ` Björn Lindström
2005-09-21 14:49     ` Ted Zlatanov
2005-09-21 14:58       ` Björn Lindström
2005-09-21 18:19         ` Ted Zlatanov
2005-09-21 19:40           ` Simon Josefsson
2005-09-27 19:38             ` Ted Zlatanov
2005-09-29 17:54               ` Simon Josefsson
2005-09-29 18:49                 ` Björn Lindström
2005-09-30  0:18                   ` Simon Josefsson
2005-09-30 10:09                     ` Björn Lindström
2005-10-04 18:04                     ` Ted Zlatanov [this message]

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=4n64sdjgzr.fsf@lifelogs.com \
    --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).