[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: |
Thu, 10 Sep 2020 15:04:26 +0530 |
Gregory Heytings <ghe@sdf.org> writes:
>>> Is there a way to tell gnus-agent to create only a cache of headers,
>>> that is, to not store a local copy of the emails that have been read?
>>
>> I don't think it does. From info '(gnus)Agent Caveats':
>>
>>> “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's what the doc says, and I'm not sure what it means exactly, but with
> the current version of Gnus, and with `gnus-select-article-hook' set to
> nil (the default), a local copy of the emails is indeed entered into the
> agent cache, by `gnus-agent-store-article'. The backtrace is
You should reset the default agent category predicate from 'short' to
'false' if you havent. See '(gnus)Category Syntax' for details.
Used to work properly for me when I had it set up like that. I'm using 26.3.
--
Ozhap
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, 2020/09/10