Re: nnimap usage model

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

David Abrahams <dave@boost-consulting.com> writes:

> That helps a bit, but I'm still in the dark.  If I had
> gnus-agent-cache == nil (the default),

It seems that the default is t, not nil.

> I wouldn't be able to use `J s'?  Or what?

Well, err.  As I understand it, frobbing gnus-agent-cache influences
the behavior for the plugged case only.  So you could set
gnus-agent-cache to nil, then you could use `J s' to fetch articles
and headers.  But as long as you're online, Gnus won't use those
local copies when you enter a group and so on.  Instead, the headers
will be fetched again.  When you go unplugged, the local copies will
be used, of course -- Gnus can't use the remote ones, after all.

Suppose you're online.  You enter a group, then quit it, then enter
it again.

When gnus-agent-cache is nil, then Gnus will fetch headers from the
server, show the summary buffer.  Then you quit the summary.  Then
you enter it again and Gnus will fetch the headers from the server
again.

When gnus-agent-cache is t, then Gnus will fetch headers from the
server, then show the summary buffer.  Gnus will also store the
just-fetched headers locally.  Then after you exit and then re-enter
the group, Gnus will use the local copies of the headers, instead of
fetching them again.

I'm not sure whether Gnus will store the just-fetched headers locally
only when gnus-agent-cache is t, or whether this storing also happens
when gnus-agent-cache is nil.  Any expert out there?

Maybe the documentation should be improved.

-- 
A turnip curses Elvis