From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings via Users list for the GNU Emacs text editor Newsgroups: gmane.emacs.help Subject: Re: Gnus: caching message headers? Date: Mon, 07 Sep 2020 17:10:42 +0000 Message-ID: References: <874ko9sgcn.fsf@ericabrahamsen.net> Reply-To: Gregory Heytings Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35755"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Alpine 2.22 (NEB 394 2020-01-19) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Mon Sep 07 19:11:10 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 1kFKfe-0009F9-B8 for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 07 Sep 2020 19:11:10 +0200 Original-Received: from localhost ([::1]:50254 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kFKfd-0001KM-De for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 07 Sep 2020 13:11:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54940) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kFKfL-0001Ji-Nx for help-gnu-emacs@gnu.org; Mon, 07 Sep 2020 13:10:51 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:62778) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kFKfJ-0003of-Eo for help-gnu-emacs@gnu.org; Mon, 07 Sep 2020 13:10:51 -0400 Original-Received: from sdf.org (IDENT:ghe@faeroes.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 087HAiek000808 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Mon, 7 Sep 2020 17:10:44 GMT Original-Received: (from ghe@localhost) by sdf.org (8.15.2/8.12.8/Submit) id 087HAtsh001015; Mon, 7 Sep 2020 17:10:55 GMT In-Reply-To: <874ko9sgcn.fsf@ericabrahamsen.net> Received-SPF: pass client-ip=205.166.94.24; envelope-from=ghe@sdf.org; helo=mx.sdf.org X-detected-operating-system: by eggs.gnu.org: First seen = 2020/09/07 11:23:37 X-ACL-Warn: Detected OS = ??? X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham 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:123983 Archived-At: Hi Eric, Many thanks for your answer. >> I would like to have, in the *Summary*, a complete list of the emails >> contained in a folder when I hit RET on its label. Each time I do this >> however, Gnus asks me how many articles I want to retrieve, and issues >> a "UID FETCH 1:N (UID RFC822.SIZE BODYSTRUCTURE BODY.PEEK[HEADER.FIELDS >> (...)])" IMAP command, which can take quite some time to complete when >> N is large. >> >> Is there a way to convince Gnus to cache the result of that command >> (without caching all emails), and to issue a command only for the new >> UIDs? Caching the result of that command should not eat too much disk >> space. > > No, not at the moment. You can avoid the prompt by customizing the value > of `gnus-large-newsgroup', but it's still going to retrieve all the > headers for the group. > > There's currently no way around this, as Gnus only lets you have one > active Summary buffer at a time, which means all the old data is dumped > every time you switch groups. In the back of my head I have some ideas > for removing this restriction, but it will take a long time to get > there. > I'm clearly not an expert, but would it not be enough to save and retrieve the contents of nntp-server-buffer in nnimap-retrieve-headers? Or are you thinking about a more generic solution that would work with all backends?