Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@hpc.uh.edu, jhbrown@ai.mit.edu
Subject: Re: Add hooks to Gnus on move/edit/delete?
Date: Mon, 30 Dec 2002 17:53:22 -0500	[thread overview]
Message-ID: <m3r8bzdspp.fsf@heechee.beld.net> (raw)
In-Reply-To: <84fzsfs5il.fsf@lucy.cs.uni-dortmund.de> (kai.grossjohann@uni-duisburg.de's message of "Mon, 30 Dec 2002 19:53:06 +0100")

On Mon, 30 Dec 2002, kai.grossjohann@uni-duisburg.de wrote:
> Well, nnmail-split-methods (or nnmail-split-fancy) could use spam.el
> to put spam messages into a special group.  spam.el could invoke
> ifile, telling it to use ~/.idata.spam.  After this, `normal'
> ifile-gnus processing could be done on the remaining ham.

On second thought, why not have something like 

(: spam-split)
(: ifile-split)

in the split rules?  It seems awkward to try to make spam.el sort mail
in a way that it wasn't intended to do.  I think I'd like to keep
functions invoked by spam-split standardized, returning either
spam-split-group or nil.  Currently, spam-check-ifile does that:

	(let ((ifile-primary-spam-group spam-split-group))
	  (ifile-spam-filter nil))))

I think that standardization would make life easier in the long run.
Do you or anyone else think we should have spam.el do general mail
sorting?

Also, the following is at Jeremy Brown's ifile-gnus.el page at
http://www.ai.mit.edu/people/jhbrown/ifile-gnus.html:

"THIS IS ALPHA-QUALITY SOFTWARE. IT MAY EAT YOUR EMAIL. IT MAY CORRUPT
YOUR GNUS CONFIGURATION. IT MAY DO OTHER UNPLEASANT THINGS TO YOUR
COMPUTER. I'M NOT KIDDING."

Considering that and the lack of support for nnimap, I'm not sure how
much work I should put into ifile-gnus.el support now instead of
later, when the code is more beta- than alpha-quality.  I'm not
implying that ifile-gnus.el is buggy, only that it may change
significantly with the next release.  Maybe Jeremy could give us an
update :)

Ted





  reply	other threads:[~2002-12-30 22:53 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
2002-12-30  3:33         ` Ted Zlatanov
2002-12-30 18:53           ` Kai Großjohann
2002-12-30 22:53             ` Ted Zlatanov [this message]
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=m3r8bzdspp.fsf@heechee.beld.net \
    --to=tzz@lifelogs.com \
    --cc=ding@hpc.uh.edu \
    --cc=jhbrown@ai.mit.edu \
    /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).