Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: What's wrong with my spam.el settings now?
Date: Thu, 29 Sep 2005 19:54:33 +0200	[thread overview]
Message-ID: <ilumzlvkbdy.fsf@latte.josefsson.org> (raw)
In-Reply-To: <4n64smz4gg.fsf@lifelogs.com> (Ted Zlatanov's message of "27 Sep 2005 15:38:23 -0400")

"Ted Zlatanov" <tzz@lifelogs.com> writes:

> On Wed, 21 Sep 2005, jas@extundo.com wrote:
>
>> How is spam.el setting the spam mark?  In particular, is it using the
>> gnus-request-set-mark interface?  That interface must be called with
>> the flag update whenever any code that alter message flags without
>> going through the summary buffer variables (which are turned into
>> gnus-request-set-mark calls when exiting the group).
>
> I do it with gnus-summary-mark-article:
>
> 5 matches for "mark-article" in buffer: spam.el
>    1325:	    (gnus-summary-mark-article article gnus-spam-mark))
>    1387:      (gnus-summary-mark-article article gnus-expirable-mark)))
>    1427:	    (gnus-summary-mark-article article gnus-unread-mark))
>    1432:	    (gnus-summary-mark-article article gnus-expirable-mark))
>    1708:		 (gnus-summary-mark-article article gnus-spam-mark))
>
> which worked fine so far.
>
> If that's wrong, what's the right way to do it (if you can point me to
> code that does the right thing, I'll make sure to implement mine the
> same way)?
>
>> If the spam mark should never be synced across Gnus installations,
>> then it should be added to gnus-article-unpropagated-mark-lists, then
>> the nnml code will not revert the spam flag.  However, it seems like
>> the spam mark should be synchronized between Gnus installations,
>> should it not?  Then the spam.el code has to call the g-r-s-m
>> interface when updating the marks.
>
> The spam mark is ephemeral, it only matters for the duration of a
> summary visit.  When you exit, spam-marked articles get processed and
> expired.  I did this intentionally when I started writing the spam.el
> logic.

Ok, this all looks good.  I misunderstood the original report.  The
problem seem to be with the seen/unseen mark, not the spam mark.
Björn, how are you quitting the group?  Are you exiting it with 'q' to
save the marks?  If you type G E on the group before entering, and
save the list of articles associated with 'seen', then enter the group
and read a few articles and quit the group using 'q', and press G E
again, do the 'seen' list look the same?

What is your general setup?  Is your ~/News/marks directory read-only
somehow?

I don't recall any reports of seen/unseen troubles like this at all.



  reply	other threads:[~2005-09-29 17:54 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 [this message]
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

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=ilumzlvkbdy.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    /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).