Re: Article caching question

[Eze Ogwuma <typhoon@dircon.co.uk>]

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

> >>>>> On 07 Jan 1998, Eze Ogwuma said:
> 
>   Eze> If I turn on article caching and gnus-asynchronous but not
>   Eze> gnus-jog-cache will gnus store *all* the articles that are
>   Eze> pre-fetched in the cache until they are read?

> You seem to want to do offline news reading.  For this, Quassia has
> the "agent" feature.  See the manual for details (I've never used it).

Thanks for the reply Kai,

I've only just started to experiment with Gnus unplugged today. What I
really want to do is to speed things up for normal news reading.

I want to have gnus pre-fetch articles in the group I happen to be
reading and hold them on the local hard disk so that I can read them
without having to wait for Gnus to fetch each article.

I also want to be able to move back and forth in the buffer without
having to wait for an article I've already read (or one that was
previously fetched but is unread) to be fetched again.

I don't know if you've ever used the program Knews but right now I use 
that for News reading and Gnus for Mail because Knews does things like 
storing information about the groups on the local hard disk between
sessions, including thread information. It also has a trail-ahead-cache 
and a cache of previously read articles. This makes it very fast over
a modem.

I've been using various combinations of gnus-asynchronous
gnus-keep-backlog and gnus-use-cache to try to duplicate this
behavior.

However I've found that Gnus will still fetch a previously fetched
article when that article is uuencoded.

i.e. In a buffer with 100 articles if I read (and uudecode (X u)) articles
9-20 then go back and uudecode and save (X U) article 10 Gnus still
fetches article 10 again.
-- 
Eze Ogwuma