Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: convert from setq to customization
Date: Fri, 07 Mar 2003 17:36:12 +0100	[thread overview]
Message-ID: <ilusmtz3zib.fsf@latte.josefsson.org> (raw)
In-Reply-To: <4nzno7w3nf.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Fri, 07 Mar 2003 11:19:16 -0500")

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Thu, 06 Mar 2003, jas@extundo.com wrote:
>> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>>> For example, spam.el requires nnimap-split-download-body in
>>> nnimap.el to be set if a statistical filter is selected, so the
>>> whole message body is downloaded.
>> 
>> This crossed my mind as well... spam.el should not setq n-s-d-b.
>> 
>> Either spam.el should bind the variable temporarily, or if that
>> doesn't work, we can add a undocumented variable nnimap-using-spam
>> which spam.el can set instead.
>
> How about spam.el generating an error if n-s-d-b is nil and a
> statistical splitter function is selected?  What kind of error is
> reasonable, a showstopper (error) or a Gnus message?  I am not sure
> because this is not a critical problem, it only means that incoming
> spam may not be properly classified.

Yes, an error seems too much.  Using a separate, non-customized,
nnimap variable that spam.el can set seems like a better approach, and
this approach is used in similar situations already.  It would also
allow people to set n-s-d-b to override the spam.el decision, if they
wanted that.

> Also, can I set n-s-d-b in the middle of splitting, or does it have
> to be set at the beginning of the IMAP conversation with the server?

It is only used by n-request-scan, and it can be set and changed at
any point.

> If I could set it, I could ask the user if he wants to set it
> automatically, and then come back and resume splitting.  Hmm, but
> then the IMAP session might time out.

But you would need to remember the decision so it isn't asked every
time...  the solution above seems better, IMHO.




  reply	other threads:[~2003-03-07 16:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-01 21:20 Randal L. Schwartz
2003-03-01 23:59 ` Ted Zlatanov
2003-03-03 13:41   ` Kai Großjohann
2003-03-03 15:56     ` Ted Zlatanov
2003-03-03 16:53       ` Kai Großjohann
2003-03-03 19:42         ` Randal L. Schwartz
2003-03-03 19:51           ` Kai Großjohann
2003-03-03 20:50           ` Randal L. Schwartz
2003-03-05 12:49   ` Per Abrahamsen
2003-03-05 20:38     ` Ted Zlatanov
2003-03-05 13:31 ` Per Abrahamsen
2003-03-05 17:38   ` David S Goldberg
2003-03-06  8:01     ` Per Abrahamsen
2003-03-05 18:39   ` Reiner Steib
2003-03-06  7:55     ` Per Abrahamsen
     [not found]   ` <4nadg9fsw2.fsf@lockgroove.bwh.harvard.edu>
     [not found]     ` <rju1ehc501.fsf@zuse.dina.kvl.dk>
2003-03-06 17:56       ` Ted Zlatanov
2003-03-06 20:13         ` Simon Josefsson
2003-03-07 16:19           ` Ted Zlatanov
2003-03-07 16:36             ` Simon Josefsson [this message]
2003-03-07 17:33               ` Ted Zlatanov
2003-03-07 18:38                 ` Simon Josefsson
2003-03-07 19:46                   ` Ted Zlatanov
2003-03-07  9:02         ` Per Abrahamsen

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=ilusmtz3zib.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).