From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Improving the spam.el documentation.
Date: 8 Jun 2004 10:31:46 -0400 [thread overview]
Message-ID: <4nfz96qfxp.fsf@lifelogs.com> (raw)
In-Reply-To: <87ekoqu9ac.fsf@enki.rimspace.net> (Daniel Pittman's message of "Tue, 08 Jun 2004 11:29:31 +1000")
On Tue, 08 Jun 2004, daniel@rimspace.net wrote:
> It occurred to me today that it might be a bit easier for people to deal
> with the spam and ham processors in the from of two group parameters,
> `spam-process' and `ham-process', rather than `spam-process' having a
> `spam' or `ham' designator before each processor...
>
> I don't know, though, if it is worth the trouble of changing over.
Definitely not, it's fine the way it is. The "spam-" prefix refers
to the spam.el package. It would be a major inconvenience, since I
just introduced the "new" format and I assume at least a few users
are using it. The "new" format:
(spam spam-use-BACKEND)
(ham spam-use-BACKEND)
makes sense when combined with the spam-use-BACKEND variables already
in spam.el. Also, it's extensible, and I plan to have
(both spam-use-BACKEND)
as an alternative, meaning "use both the ham and the spam processors"
as a shortcut for specifying both versions of the processor. This
will probably come in the spam.el redesign.
Ted
next prev parent reply other threads:[~2004-06-08 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 13:26 Daniel Pittman
2004-05-28 15:00 ` Jesper Harder
2004-05-28 16:27 ` Ted Zlatanov
2004-05-31 13:34 ` Daniel Pittman
2004-06-07 16:56 ` Ted Zlatanov
2004-06-08 1:29 ` Daniel Pittman
2004-06-08 14:31 ` Ted Zlatanov [this message]
2004-06-07 17:06 ` Ted Zlatanov
2004-06-08 1:38 ` Daniel Pittman
2004-06-08 2:25 ` Jesper Harder
2004-06-08 3:28 ` Daniel Pittman
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=4nfz96qfxp.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).