From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Madhu Newsgroups: gmane.emacs.help Subject: Re: Gnus: caching message headers? Date: Sun, 04 Oct 2020 14:42:32 +0530 Message-ID: References: <87imclnqsz.fsf@Kittu.i-did-not-set--mail-host-address--so-tickle-me> <87ft7ngbrv.fsf@ericabrahamsen.net> <87wo0ytwy5.fsf@Kittu.i-did-not-set--mail-host-address--so-tickle-me> <87lfheefq4.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34821"; mail-complaints-to="usenet@ciao.gmane.io" To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Sun Oct 04 11:56:03 2020 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kP0kN-0008vk-2l for geh-help-gnu-emacs@m.gmane-mx.org; Sun, 04 Oct 2020 11:56:03 +0200 Original-Received: from localhost ([::1]:49790 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kP0kM-0004DU-4p for geh-help-gnu-emacs@m.gmane-mx.org; Sun, 04 Oct 2020 05:56:02 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39062) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kP0jy-0004D7-Ud for help-gnu-emacs@gnu.org; Sun, 04 Oct 2020 05:55:38 -0400 Original-Received: from [117.193.9.198] (port=49320 helo=localhost.localdomain) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kP0jw-0004c5-GE for help-gnu-emacs@gnu.org; Sun, 04 Oct 2020 05:55:38 -0400 Original-Received: (qmail 14586 invoked by uid 500); 4 Oct 2020 09:12:32 -0000 In-Reply-To: <87lfheefq4.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sat, 12 Sep 2020 16:29:39 -0700") X-Host-Lookup-Failed: Reverse DNS lookup failed for 117.193.9.198 (failed) Received-SPF: softfail client-ip=117.193.9.198; envelope-from=enometh@meer.net; helo=localhost.localdomain X-detected-operating-system: by eggs.gnu.org: First seen = 2020/10/04 05:12:58 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x (no timestamps) [generic] [fuzzy] X-Spam_score_int: 29 X-Spam_score: 2.9 X-Spam_bar: ++ X-Spam_report: (2.9 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_PBL=3.335, RCVD_IN_SORBS_DUL=0.001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:124267 Archived-At: * Eric Abrahamsen <87lfheefq4.fsf@ericabrahamsen.net> : Wrote on Sat, 12 Sep 2020 16:29:39 -0700: > Ozhap writes: > >> Eric Abrahamsen writes: >> >>> Ozhap writes: >>> >>>>>> "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 >>> >>> If I were you I would do this up as a proper bug report. Lars is now >>> an Emacs maintainer, so he'll be obliged to look at it :) >>> >>> One way or another there is a mismatch between documentation, >>> customization options, and actual observed behavior. I think if you >>> can make it clear what that mismatch is, we stand a good chance of >>> getting it fixed. >> >> Here you go. I think I did good :) >> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=43356 > > I saw it, I agree it's good! Lars followed the instructions like a good boy and and has obsoleted gnus-agent-store-article and removed that functionality. | commit def34a20766ea5179afd5e5ed090a2b86fcccb5e | Author: Lars Ingebrigtsen | AuthorDate: Sun Sep 13 16:46:11 2020 +0200 | | "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'. | However the overhead of calling gnus-agent-fetch-selected-article is too much in my 100s of (NNTP) news groups and the several thousands of articles with complicated reading history. "Yuuge lists of gnus cons data structures". The overhead is not acceptable. The earlier behaviour was exactly what I wanted for NNTP (I dont use gnus for mail) and I have been using the feature on selective servers ever since it was added, relying on gnus to back up my memory (If I read an article gnus can help me remember where I read it). I don't give a shit about gmail users and I'd suggest reverting it unobsoleting gnus-agent-store-article and yet another switch for those who want to keep the original very useful behaviour code path. For those who prefer to control their own data instead of selling it (along with their access patterns and their souls) to google.