From: Ozhap <ozhap@vollbio.de>
To: Gregory Heytings <ghe@sdf.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Gnus: caching message headers?
Date: Thu, 10 Sep 2020 15:15:09 +0530 [thread overview]
Message-ID: <87imcm0xui.fsf@Kittu.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87lfhi0ycd.fsf@Kittu.i-did-not-set--mail-host-address--so-tickle-me>
Ozhap <ozhap@vollbio.de> writes:
> 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.
Scratch that. I guess it's only for gnus-agent-fetch-session.
> Used to work properly for me when I had it set up like that. I'm using 26.3.
In fact I was once trying to get the opposite behaviour to your desired
one - to store read emails, which was not happening by default. And
finally achieved it with the above option.
--
Ozhap
next prev parent reply other threads:[~2020-09-10 9:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 8:38 Gnus: caching message headers? Ozhap
2020-09-10 9:00 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-09-10 9:34 ` Ozhap
2020-09-10 9:45 ` Ozhap [this message]
2020-09-10 13:16 ` wgreenhouse
-- strict thread matches above, loose matches on Subject: below --
2020-10-08 3:28 Ozhap
2020-10-08 1:59 Ozhap
2020-10-07 11:39 Ozhap
2020-09-10 23:41 Ozhap
2020-09-11 22:59 ` Eric Abrahamsen
2020-09-12 23:08 ` Ozhap
2020-09-12 23:29 ` Eric Abrahamsen
2020-10-04 9:12 ` Madhu
2020-09-07 15:23 Gregory Heytings via Users list for the GNU Emacs text editor
2020-09-07 16:26 ` Eric Abrahamsen
2020-09-07 17:10 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-09-07 17:37 ` Eric Abrahamsen
2020-09-07 17:49 ` wgreenhouse
2020-09-08 13:19 ` Eric S Fraga
2020-09-08 13:37 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-09-08 14:34 ` Stefan Monnier
2020-09-08 17:29 ` Eric Abrahamsen
2020-09-08 21:52 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-09-08 22:33 ` Stefan Monnier
2020-09-08 16:12 ` wgreenhouse
2020-09-08 20:39 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-09-07 17:50 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-09-07 17:53 ` Eric Abrahamsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imcm0xui.fsf@Kittu.i-did-not-set--mail-host-address--so-tickle-me \
--to=ozhap@vollbio.de \
--cc=ghe@sdf.org \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).