Re: Make gnus-agent default to t?

[Simon Josefsson <jas@extundo.com>]

Simon Josefsson <jas@extundo.com> writes:

> prj@po.cwru.edu (Paul Jarc) writes:
>
>> Simon Josefsson <jas@extundo.com> wrote:
>>>> gnus-agent's value is t
>>>
>>> This is now the default.
>>
>> nnmaildir users may want to set this to nil for a while; I'm still
>> working on making article numbers persistent, so header caching could
>> break right now.
>
> I forgot about that.  Hm.  Perhaps extending `gnus-agent-cache' so it
> can exclude certain groups would be useful?  Then it could default to
> cache everything for all groups except nnmaildir groups (until
> nnmaildir gets persistent article numbers).  What do you think?

Never mind, there's no need for panic, or setting `gnus-agent' to nil:

Agent NOV caching doesn't make sense for local servers at all, does
it?

I think nnmaildir users would only have problems if they had agentized
the nnmaildir server.  Since that didn't work in the past (the agent
really require persistant article numbers), there is no change.

Don't add nnmaildir servers to the agent.

Try running nnmaildir with `gnus-agent' at its default value.  There
should be no ~/News/agent/nnmaildir hierarchy.  If there is, there
will be problems.  Otherwise, you're safe.

OTOH users must enroll their remote secondary nntp and nnimap servers
with the agent to gain the NOV caching feature.  This should probably
happen by default, but only for nntp and nnimap?

Hm.  Agent NOV caching would obsolete nnfolder NOVs, wouldn't it?