Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: spam-split doesn't split
Date: Fri, 12 Dec 2003 16:56:43 -0500	[thread overview]
Message-ID: <4nfzfp8ztw.fsf@collins.bwh.harvard.edu> (raw)
In-Reply-To: <86oeufszbi.fsf@oumu.wohnheimb.uni-frankfurt.de> (Adam Duck's message of "Fri, 12 Dec 2003 00:35:13 +0100")

On Fri, 12 Dec 2003, duck@informatik.uni-frankfurt.de wrote:

> I have to say that I'm already using gnus-cvs and emacs-cvs (it's in
> portage on gentoo). Still, `spam-split' is not moving spam.

Try increasing gnus-verbose to 10 and see what is in the *Messages*
buffer.

You can put (debug) statements in the spam-split function, then
re-evaluate it with C-x C-e and you'll get popped to the debugger at
those times.  Hit `c' to continue.  You can use (debug A B C) where
A B C are any Elisp objects, and you'll be able to see their values
when you go to the debugger.  You can also put (debug) statements in
spam-check-bogofilter, which may be more understandable.  spam-split
is a pretty confusing function.  All of this is in the spam.el
library.

There is another, more interactive debugger but I'm not sure we need
to go there yet.

Finally, Xavier brought up a good point - is gentoo's portage a few
steps behind CVS or is it the latest CVS?  I've never used portage.

Thanks
Ted



  parent reply	other threads:[~2003-12-12 21:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-09 18:07 Adam Duck
2003-12-09 22:29 ` Ted Zlatanov
2003-12-11 16:16   ` Adam Duck
2003-12-11 19:15     ` Ted Zlatanov
2003-12-11 23:35       ` Adam Duck
2003-12-12 18:28         ` Xavier Maillard
2003-12-12 21:56         ` Ted Zlatanov [this message]
2003-12-13 10:29           ` Adam Duck
2003-12-13 17:54             ` Xavier Maillard

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=4nfzfp8ztw.fsf@collins.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).