Re: Entering nnimap group got much slower with 5.10

[kai.grossjohann@gmx.net (Kai Großjohann)]

Lloyd Zusman <ljz@asfast.com> writes:

> Could someone explain to me what would be different about my day-to-day
> Gnus experience if I start to agentize nnimap?

Well, agentizing means that you can use Agent commands.  You don't
have to use them, but if you don't use any Agent commands, the
corresponding action will not happen.

But I think that the Agent will function as a header cache out of the
box, without having to execute any extra commands at all.  This means
that Gnus will download the headers when you first enter a group and
cache them locally.  Then, when you enter the group again, Gnus will
use the headers from the local cache and only download the headers
that are missing from the local cache.

You can also tell Gnus to download all articles that you read and
cache them locally.  This means that looking at those articles a
second time will be faster.  But this is not the default
configuration, you have to add a line to ~/.gnus.

Everything else requires that you press new keys.

But it's not that difficult.  Here is how I normally use Gnus when I
commute:

(1) I start Emacs and Gnus (in plugged mode, ie, normally).
(2) I hit `J s' to tell Gnus to fetch all articles.
(3) I hit `J j' to go unplugged and then hibernate my laptop.
(4) In the train, I wake up the laptop and read the previously-
    downloaded articles and respond to them and so on.
(5) At the end of the train ride, I hibernate the laptop again.
(6) In the office, I do `J j' to go plugged.  Then I use `J S' to
    send all mails and postings composed in the train.

So the only Agent-specific keys I hit during the whole session are
these:  `J s' -- `J j' -- `J j' -- `J S'

I find that rather convenient, considering that it gives me offline
functionality.

-- 
file-error; Data: (Opening input file no such file or directory ~/.signature)