From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: spam.el: automatically resplitting ham in a spam group?
Date: Sun, 23 Nov 2003 00:43:22 -0500 [thread overview]
Message-ID: <4nbrr3skqt.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <lorentey.g.ding.877k1u7vh7.elte@eris.elte.hu> =?utf-8?q?=28L=C5=91rentey_K=C3=A1roly's?= message of "Thu, 20 Nov 2003 19:20:20 +0100")
On Thu, 20 Nov 2003, lorentey@elte.hu wrote:
> But if I understand it well, no message would be lost; they would
> just reappear in the current group, and I think these users can
> easily fix their configuration, or simply ignore the new respooling
> feature. Adding a note to the documentation along the lines of 'to
> prevent unexpected results, if you plan to use this feature, make
> sure that your split rules are set up so that the last rule never
> returns nil' would be enough, I guess.
Well, don't forget that nnimap is buggy with respooling - I always
see nil as the respool result, no matter what. I will leave things
the way they are for now, and fix any obvious bugs but generally I'll
leave further work in this direction until No Gnus.
> (By the way: is it 'respool' or 'resplit'? I don't know the correct
> terminology.)
The respooling should invoke the splitting functions, thus
resplitting the article :)
> I have played with it for a while, and after adding the
> no-spam-split-during-respool thingy, I think it does exactly what I
> need.
>
> If you're interested, here is my change: (it's quite ugly, but
> works)
I didn't see this until I had done quite a bit of work on spam.el
in a different direction, so I'm afraid your patch won't work
cleanly. Can you check your patch against the mega-patch I'll be
posting later tonight and see if there are any conflicts? Thanks!
Ted
next prev parent reply other threads:[~2003-11-23 5:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 15:14 Lőrentey Károly
2003-11-19 20:48 ` Ted Zlatanov
2003-11-19 20:57 ` Jody Klymak
2003-11-19 21:24 ` Ted Zlatanov
2003-11-19 21:48 ` Reiner Steib
2003-11-19 21:58 ` Jody Klymak
2003-11-20 11:17 ` Ted Zlatanov
2003-11-20 14:46 ` Jake Colman
2003-11-20 12:19 ` Lőrentey Károly
2003-11-20 12:48 ` Lőrentey Károly
2003-11-20 13:33 ` Ted Zlatanov
2003-11-20 15:48 ` Lőrentey Károly
2003-11-20 16:22 ` Ted Zlatanov
2003-11-20 18:20 ` Lőrentey Károly
2003-11-23 5:43 ` Ted Zlatanov [this message]
2003-12-09 2:02 ` Lőrentey Károly
2003-12-09 22:20 ` Ted Zlatanov
2003-12-09 22:57 ` Lőrentey Károly
2003-12-10 19:57 ` Ted Zlatanov
2003-11-20 13:28 ` Ted Zlatanov
2003-11-20 18:42 ` Lőrentey Károly
2003-11-19 21:51 ` Kai Grossjohann
2003-11-19 21:53 ` Kai Grossjohann
2003-11-19 22:05 ` Josh Huber
2003-11-20 20:30 ` Kai Grossjohann
2003-11-20 21:07 ` Josh Huber
2003-11-20 14:48 ` Jake Colman
2003-11-20 11:22 ` Ted Zlatanov
2003-11-20 12:31 ` Lőrentey Károly
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=4nbrr3skqt.fsf@lockgroove.bwh.harvard.edu \
--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).