Re: New agent code

[kai.grossjohann@uni-duisburg.de (Kai Großjohann)]

Kevin Greiner <kgreiner@xpediantsolutions.com> writes:

> The intended behavior is as follows:
> If an article was fetched into the agent's cache, then the article's
> header will be removed from the overview at the same time as the
> article is expired.
> If an article was never fetched, then the article's header will be
> removed from the overview if the article is marked as read but not
> marked as ticked nor dormant.
> If an article is in the overview, but not in the agentview, remove it
> from the overview.
>
> The first rule is probably obvious.  The second rule exists because
> gnus-agent doesn't currently keep a timestamp on when a header was
> fetched.  As a result, I can't expire just a header using
> gnus-agent-expire-days.  The third rule cleans up an overview that has
> gotten out-of-sync with its agentview.

Does the rest of the expiry code go by the fetched date or by the
article date?

Normal (mail) expiry also confuses these two times (date header of
message; timestamp of nnml file on disk; time when user hits E -- Kai
can't cound).  So maybe it's not so bad when the agent does the
same.

But OTOH, if the articles are expired by elapsed time since
fetching and the headers are expired by elapsed time since their
date, that would be strange.

Hm.

-- 
~/.signature is: umop ap!sdn    (Frank Nobis)