Re: No Gnus doesn't like the obsolete spam syntax

["Ted Zlatanov" <tzz@lifelogs.com>]

On Tue, 09 Aug 2005, rra@stanford.edu wrote:

> Just a quick note in case it saves someone else some time.
> 
> I used to have:
> 
> (custom-set-variables
>  '(gnus-parameters
>    '(("^nnml:spam\\..*"
>       (spam-contents gnus-group-spam-classification-spam)
>       (spam-process (gnus-group-spam-exit-processor-bogofilter
>                      gnus-group-ham-exit-processor-bogofilter))))))
> 
> (with more gnus-parameters, but that's the relevant ones).  This no longer
> works with No Gnus (version in the headers).  I'm not entirely sure why,
> but following the manual's instructions and then fiddling a little to
> figure out what they really mean, the following *does* work:
> 
> (custom-set-variables
>  '(gnus-parameters
>    '(("^nnml:spam\\..*"
>       (spam-contents gnus-group-spam-classification-spam)
>       (spam-process ((spam spam-use-bogofilter)
>                      (ham spam-use-bogofilter)))))))
> 
> It took me a little bit to get the syntax right, since for some reason I
> read the manual suggestion and thought it said to replace
> 
>     gnus-group-spam-exit-processor-bogofilter
> 
> with
> 
>     ('(spam spam-use-bogofilter))
> 
> literally.  That just silently fails with no error message, apparently due
> to having one too many layers of parens.

Yeah...  I wasn't sure about changing to the new style of
configuration for exactly this reason - backwards compatibility.  I
think the pain is worth it, though, as the new format is much better
IMO.

Was the manual misleading in any way?  I'll be glad to fix it.

> (Yes, I know you can do this all inside customize.  I hate the interface
> for customize and also prefer to have commented configurations so that I
> can remember why I changed something, which means that I do a lot of
> writing code based directly on the manual or using customize to generate a
> first draft and then tweaking it.)

I'm ambivalent on this issue.  It's nice to customize, and for spam.el
stuff it's almost required, but on the other hand I like everything in
my gnus.el...  Of course, don't forget that Gnus has three ways to set
group variables, through gnus-parameters, individual global variables,
and group/topic parameters...  It's insane IMHO.  I would prefer to
pick one (group/topic parameters are best I think) and provide
conversion functions from the others to it.  But anyhow :)

Ted