unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Ozhap <ozhap@vollbio.de>
To: wgreenhouse@tilde.club
Cc: help-gnu-emacs@gnu.org
Subject: Re: Gnus: caching message headers?
Date: Fri, 11 Sep 2020 05:11:00 +0530	[thread overview]
Message-ID: <87imclnqsz.fsf@Kittu.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: s8ba6xx22mb.fsf@tilde.club

>> “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



             reply	other threads:[~2020-09-10 23:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10 23:41 Ozhap [this message]
2020-09-11 22:59 ` Gnus: caching message headers? Eric Abrahamsen
2020-09-12 23:08   ` Ozhap
2020-09-12 23:29     ` Eric Abrahamsen
2020-10-04  9:12       ` Madhu
  -- 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  8:38 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
2020-09-10 13:16   ` wgreenhouse
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=87imclnqsz.fsf@Kittu.i-did-not-set--mail-host-address--so-tickle-me \
    --to=ozhap@vollbio.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=wgreenhouse@tilde.club \
    /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).