Re: Idea for turbo expiry

[Jason L Tibbitts III <tibbs@hpc.uh.edu>]

>>>>> "DM" == David Moore <dmoore@UCSD.EDU> writes:

DM> I was thinking a good thing to do would be to get a list of all of the
DM> files in the directory and intersect that list with the read list, and
DM> only remove things in the intersection.

Is it really true that Gnus doesn't know the difference between articles
that are read but not expired and articles that are completely gone?  I can
understand why the front end wouldn't care, but the backend has to have a
way to figure it out without going through the directory.  Couldn't it use
the overview file if available?  I think that would be quicker iterating
through the directory.

I still think it would be worthwhile to let the user choose to assume
chronological ordering so that expiry can bail early.  I have groups with
really long expiry times, like a year, and some of them hold upwards of ten
thousand articles.  These take _forever_ to process.  (I've been using Gnus
since (ding) Gnus Warp 0.6 and have processed a _lot_ of mail through it.)

 - J<