Re: Not running expiry when I exit a group

[David Moore <dmoore@UCSD.EDU>]

Kai Grossjohann <grossjohann@charly.cs.uni-dortmund.de> writes:

> >>>>> David Moore writes:
> 
>   David> If you use total-expire, Gnus loops over every article in the
>   David> "active range" checking the dates on the files to see if they
>   David> should be expired.  If you have an old ticked or cached
>   David> article the active range can be huge.
> 
> Does Gnus behave differently with auto-expire?  How is the behavior
> different?

With auto-expire (or manually marking things E), Gnus just removes the
files marked E.  Even if you have a large range, only articles recently
marked E should still be in the list, so it should go faster.
total-expire tries checking every article in the range.

But then again, I don't use auto-expire anymore, as it took too much
thinking about, and doesn't work well with scoring.

> Does one need to mark articles as "read" rather than "dormant" or
> "ticked" in order to benefit from the improvements from changing from
> total-expire to auto-expire?

If you use auto-expire you should get expiry benefits w/o changing those 
things, as it just looks only at the articles marked as expirable.  But
then things like adaptive scoring breaks.