From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: Add hooks to Gnus on move/edit/delete?
Date: Mon, 30 Dec 2002 19:49:51 +0100 [thread overview]
Message-ID: <84isxbs5o0.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3n0mov3mu.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
>
>> I'm not sure. How do I tell spam.el which group a message is in? If
>> ifile has chosen the group wrongly, how do I tell it about the error?
>
> Quoth the manual:
>[...]
> So I guess spam.el tells ifile these things upon group exit...
Hm. I'll read it again, but I thought spam.el only distinguished
between spam and ham, not between N different groups.
spam.el can use ifile as a binary classifier, but ifile-gnus.el
allows for using ifile as a multiway classifier. (Whee. Does that
make sense?)
--
Ambibibentists unite!
next prev parent reply other threads:[~2002-12-30 18:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 16:17 Kai Großjohann
2002-09-10 18:17 ` Jeremy H. Brown
2002-09-10 20:04 ` Kai Großjohann
2002-09-10 21:03 ` Jeremy H. Brown
2002-09-12 18:07 ` Clemens Fischer
2002-09-13 4:25 ` Jeremy H. Brown
2002-12-29 17:43 ` Lars Magne Ingebrigtsen
2002-12-29 18:34 ` Kai Großjohann
2002-12-29 18:44 ` Lars Magne Ingebrigtsen
2002-12-29 19:14 ` Ted Zlatanov
2002-12-29 22:06 ` Kai Großjohann
2002-12-29 22:53 ` Lars Magne Ingebrigtsen
2002-12-30 3:35 ` Ted Zlatanov
2002-12-30 18:49 ` Kai Großjohann [this message]
2002-12-30 3:33 ` Ted Zlatanov
2002-12-30 18:53 ` Kai Großjohann
2002-12-30 22:53 ` Ted Zlatanov
2002-12-31 12:08 ` Kai Großjohann
2002-12-31 14:32 ` ifile-gnus: " Ted Zlatanov
2002-12-31 19:44 ` Nathan J. Williams
2002-12-31 20:00 ` Ted Zlatanov
2003-01-02 17:29 ` Simon Josefsson
2003-01-02 21:31 ` Kai Großjohann
2003-01-02 22:07 ` Simon Josefsson
2003-01-03 13:31 ` Kai Großjohann
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=84isxbs5o0.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@uni-duisburg.de \
/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).