[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Gnus: caching message headers?
From: |
Ozhap |
Subject: |
Re: Gnus: caching message headers? |
Date: |
Fri, 11 Sep 2020 05:11:00 +0530 |
>> “If I read an article while plugged, do they get entered into the
>> Agent?”
>>
>> *No*. If you want this behavior, add
>> ‘gnus-agent-fetch-selected-article’ to ‘gnus-select-article-hook’.
> That Info page could be more explicit that `gnus-agent-cache' means that
> articles *will* be added to the agent as they are read.
That's how it stands now, but in info '(gnus)Agent as Cache' it says:
"..Gnus normally only downloads *headers* once, and stores them in the
Agent"
"Articles are *not* cached in the Agent by default though (that would
potentially consume lots of disk space), but if you have *already
downloaded an article into the Agent*, Gnus will not download the
article from the server again but use the locally stored copy instead."
I did some digging, and this behaviour was changed due to bug#8502 where
Lars concludes (erroneously, on the face of it):
> Let's see... caching... so if you're online (in an agentised group)
> and select an article, you want the article to be saved in the Agent
> directory? That sounds eminently reasonable, and I thought that was
> supposed to happen, but I can't find any code for doing that... hm...
> Nope.
Ref:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=8502
--
Ozhap
- Re: Gnus: caching message headers?, (continued)
Multiple summary buffers (was: Gnus: caching message headers?), Tim Landscheidt, 2020/09/07
Re: Gnus: caching message headers?, Ozhap, 2020/09/10
Re: Gnus: caching message headers?,
Ozhap <=