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: Tue, 31 Aug 2021 15:47:08 +0300 Message-ID: <834kb5u6gj.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> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16403"; 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 Tue Aug 31 15:16:00 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 1mL3cN-0003vN-Kh for ged-emacs-devel@m.gmane-mx.org; Tue, 31 Aug 2021 15:15:59 +0200 Original-Received: from localhost ([::1]:52280 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mL3cJ-0004ND-0W for ged-emacs-devel@m.gmane-mx.org; Tue, 31 Aug 2021 09:15:55 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38212) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mL3Aj-0005mK-To for emacs-devel@gnu.org; Tue, 31 Aug 2021 08:47:25 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:33612) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mL3Ah-0000AL-Ve for emacs-devel@gnu.org; Tue, 31 Aug 2021 08:47:24 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1943 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 1mL3Aa-0005hm-KX; Tue, 31 Aug 2021 08:47:18 -0400 In-Reply-To: (message from Richard Stallman on Mon, 30 Aug 2021 23:09:24 -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:273581 Archived-At: > From: Richard Stallman > Cc: tomas@tuxteam.de, emacs-devel@gnu.org > Date: Mon, 30 Aug 2021 23:09:24 -0400 > > > I prefer not to review a thread via a summary, because a specialized > > summary prevents me from easily seeing messages that don't satisfy the > > summary criteria. > > I am not sure what this means. A summary based on filtering will show > some messages and not others, but how is that harmful? > It sounds like you want two conflicting things -- what two things are they? > > Could you say concretely what "prevents..,from easily seeing" means? Once you request a summary based on filtering, the unfiltered summary is gone. So I can no longer quickly and conveniently look for messages that were filtered out by scrolling the summary buffer or by searching in it. Suppose a message in a thread changed the subject, enough so that neither summary by subject nor rmail-next-same-subject find it. With the unfiltered summary buffer, I can still look for it, e.g. by searching for the sender or some fragment of the Subject in the summary buffer. With summary-by-topic, I can't do that. > 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? 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? If not, then the implementation should be much more complicated, and the resulting order of the messages in the summary could be confusing, because messages could have arrived out of order, which happens when, for example, the email server was temporarily off-line. If the messages are sorted by date/time, the order will be reasonable (barring clock mismatches).