Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Spam does not move
Date: 24 Jun 2004 12:30:03 -0400	[thread overview]
Message-ID: <4nzn6s6hro.fsf@lifelogs.com> (raw)
In-Reply-To: <m3hdt8ua8f.fsf@venus.dti.ne.jp> (Kohkichi Hosoda's message of "Sat, 19 Jun 2004 01:00:46 +0900")

On Sat, 19 Jun 2004, khosoda@venus.dti.ne.jp wrote:

>>>>>> On 14 Jun 2004 12:07:45 -0400, "Ted Zlatanov" <tzz@lifelogs.com> said:
> 
> Ted> The new version of spam.el which I just posted to the ding list
> Ted> has new logic for moving spam out.  Can you test with that
> Ted> version and let me know what happens?
> 
> Unfortunately, the new version does not change the situation.   Spam
> mail marked with "O" in ham group still does not go into spam group
> when I exited the summary buffer of the ham group. 

I'm pretty sure this is not a problem with spam.el, but either with
your configuration or with another part of Gnus (maybe the agent?)

Put this:

(debug (spam-list-articles gnus-newsgroup-articles 'spam))

at line 1296 of spam.el, just before 

    ;; do the non-moving backends first, then the moving ones
    (dolist (backend-type '(non-mover mover))

Then do M-x eval-buffer, and try to repeat the behavior.

When you quit the summary, you'll see a buffer that will show you the
list of spam-marked messages.  At least one, the one you marked as
spam, should be in it, represented as an integer.  If it's not,
something is very wrong with your gnus-newsgroup-articles.  Or maybe
you've customized your spam-marks variable, though no one has ever
done that to my knowledge...

I've spent hours testing this, and I simply can't find the bug you
describe.  I don't doubt your experience, but it's very difficult to
debug a problem that I can't duplicate.  Maybe you should try
debugging the spam-summary-prepare-exit function yourself or get
someone local that knows Emacs well to help you.

Ted

(to undo the changes above, undo them in spam.el and do M-x
eval-buffer again)



  reply	other threads:[~2004-06-24 16:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 12:47 Kohkichi Hosoda
2004-05-17 15:17 ` Reiner Steib
2004-05-18 14:55   ` Kohkichi Hosoda
2004-05-18 15:40     ` Kai Grossjohann
2004-05-19 15:31       ` Kohkichi Hosoda
2004-05-19 18:07         ` Ted Zlatanov
2004-05-21 13:16           ` Kohkichi Hosoda
2004-05-22 14:11             ` Kohkichi Hosoda
2004-05-24 19:10             ` Ted Zlatanov
2004-05-28 17:00               ` Kohkichi Hosoda
2004-06-14 16:07                 ` Ted Zlatanov
2004-06-18 16:00                   ` Kohkichi Hosoda
2004-06-24 16:30                     ` Ted Zlatanov [this message]
2004-06-26 14:05                       ` Kohkichi Hosoda
2004-06-26 16:19                       ` Kohkichi Hosoda
2004-06-29 18:16                         ` Ted Zlatanov
2004-07-01 13:21                           ` Kohkichi Hosoda
2004-07-01 16:11                             ` Ted Zlatanov
2004-07-02 13:11                               ` Kohkichi Hosoda
2004-07-16 17:00                                 ` Ted Zlatanov
2004-07-25 14:29                                   ` Kohkichi Hosoda
2004-07-27 16:46                                     ` Ted Zlatanov
2004-08-14 14:15                                       ` Kohkichi Hosoda
  -- strict thread matches above, loose matches on Subject: below --
2004-05-16 13:20 Kohkichi Hosoda

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=4nzn6s6hro.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).