From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: rmail threading Date: Thu, 02 Sep 2021 09:43:59 +0300 Message-ID: <83a6kvpjdc.fsf@gnu.org> References: <87h7fcnmq0.fsf@posteo.net> <87o89kw0hl.fsf@gnus.org> <0c369b25-aedd-1fdf-4813-503f27e42c7c@yandex.ru> <874kbbznwv.fsf@gmail.com> <8735qvwcqt.fsf@gmail.com> <20210828065708.GA29375@tuxteam.de> <83o89gl8ae.fsf@gnu.org> <834kb7kue8.fsf@gnu.org> <834kb5u6gj.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4455"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Sep 02 08:44:59 2021 Return-path: Envelope-to: ged-emacs-devel@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 1mLgT4-0000pF-6e for ged-emacs-devel@m.gmane-mx.org; Thu, 02 Sep 2021 08:44:58 +0200 Original-Received: from localhost ([::1]:39010 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mLgT2-0007av-JY for ged-emacs-devel@m.gmane-mx.org; Thu, 02 Sep 2021 02:44:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49908) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mLgSJ-0006v8-7T for emacs-devel@gnu.org; Thu, 02 Sep 2021 02:44:11 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:50750) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mLgSJ-00021f-0V for emacs-devel@gnu.org; Thu, 02 Sep 2021 02:44:11 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2250 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mLgSA-0006sm-Tl; Thu, 02 Sep 2021 02:44:03 -0400 In-Reply-To: (message from Richard Stallman on Wed, 01 Sep 2021 23:37:51 -0400) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:273697 Archived-At: > From: Richard Stallman > Cc: emacs-devel@gnu.org > Date: Wed, 01 Sep 2021 23:37:51 -0400 > > This suggests we should have a convenient way to make multiple > summaries of a single Rmail buffer, and keep them in parallel. > What do you think of that? That'd help, yes. Still, the need to switch between different summary buffers is less convenient, IMO. > > > A summary in Rmail doesn't stop you from looking at messages not > > > included in it. I do that frequently. > > > Can you tell how do you do that? > > If you have the Rmail buffer selected, the summary does not affect the > ordinary Rmail commands. They move through the whole file unaffected > by the summary. Yes, of course. But that means you move by single message, which is very inconvenient when you search for something. M-s could help, but M-s still leaves you looking at the inbox through a single-message loophole. > > And I have one additional question about your request to have a > > summary-by-thread: is it okay to request that the user first sorts the > > messages by date (C-c C-s C-d), before summarizing the thread? > > That would be a pain in the neck for me. I don't want to reorder > RMAIL file. Too bad. > If you go through all the messages making a Lispy data structure that > records the most important header fields of each, and its message > number, it would be pretty easy to sort that data structure and then > find the threads in it. Then you could display the thread summary > either by send order or by order in the Rmail file. Yes, that's more or less what Gnus does. So I think the best way of doing that would be to borrow the code from Gnus. I hoped to avoid that complexity, including the need to process all the threads before one can walk a single thread. I usually leave in INBOX old messages that I need to consult frequently, so my INBOX file is very large, and processing all of it for threads could take a while.