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: [PATCH v3] Allow applying filters to summary consecutively Date: Sat, 12 Nov 2022 09:47:35 +0200 Message-ID: <83v8nkobqg.fsf@gnu.org> References: <874jvaont2.fsf@autistici.org> <83r0ybs07r.fsf@gnu.org> <83r0y9q5j1.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27465"; mail-complaints-to="usenet@ciao.gmane.io" Cc: andrea.monaco@autistici.org, rpluim@gmail.com, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Nov 12 08:48:07 2022 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 1otlFH-0006s6-LI for ged-emacs-devel@m.gmane-mx.org; Sat, 12 Nov 2022 08:48:07 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1otlEx-0000B1-Hm; Sat, 12 Nov 2022 02:47:47 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1otlEm-0000AO-NI for emacs-devel@gnu.org; Sat, 12 Nov 2022 02:47:38 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1otlEm-00061s-AQ; Sat, 12 Nov 2022 02:47:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=yod75DspLRvsXfrnjGVEoLxVr0kjO1dZoPsr9CKh6GQ=; b=e93ag/5XiSDjalomxNKT OWMDYPELAWbuv8zIiKJuqWLiYYbSexiGOPgAuanvdiUHekO4jFrFU8RS6KAmIQ6Ydv33OyEiRlhNR O0hZ3Spx7yTzBLJiIwCjPliI2FrAJ1HSGWhF4u1BBWH0HZEfLc35Q4dQR4cnSCwdhuV3MyN6Qoj/j 3vFReADFwtErk+iZGKagGGRKA1EqGdleMSt5eCJEHC7rfcuFVBpAU0TFC7EKth7suN02sd3uQ54pI Jj6QCEXkvg7G9g4wH6pcv7TN7vtYyOevD9HkPwykWMw7hM2gzdbaIR97aBmGS3DGRc/m2vgBBpQ0y IWpXapjL32nwlg==; Original-Received: from [87.69.77.57] (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 1otlEh-0003Eg-DM; Sat, 12 Nov 2022 02:47:31 -0500 In-Reply-To: (message from Richard Stallman on Fri, 11 Nov 2022 22:35:54 -0500) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:299622 Archived-At: > From: Richard Stallman > Cc: andrea.monaco@autistici.org, rpluim@gmail.com, emacs-devel@gnu.org > Date: Fri, 11 Nov 2022 22:35:54 -0500 > > > That's okay, thanks. But it's only the beginning of my problem. How > > do you describe the effect of applying a filter on top of one or more > > other filters? Andrea wants to use "intersection", but I tend to > > think this is too "mathematical" and too vague to explain clearly what > > happens. What would be a good terminology for that? > > How about "filter further"? "Filter down"> "Filter more strictly"? I have a fundamental problems with using "filtering" in this context. Existing Rmail commands that create summaries don't mention filtering at all. Here's a typical example: rmail-summary-by-topic is an interactive native-compiled Lisp function in ‘rmailsum.el’. (rmail-summary-by-topic SUBJECT &optional WHOLE-MESSAGE) Display a summary of all messages with the given SUBJECT. Normally checks just the Subject field of headers; but with prefix argument WHOLE-MESSAGE is non-nil, looks in the whole message. SUBJECT is a regular expression. So talking about "filtering" in this context will be "out of the blue", unless we also change the doc strings of all rmail-summary-by-* commands and the manual to talk about "filtering". Moreover, "filtering" is somewhat wrong: the messages themselves aren't "filtered": they aren't removed from the inbox. They are just omitted from the produced summary, and commands that move by summary lines skip messages that are not in the summary. So "filtering" here is not real, it's imaginary, and the documentation will need to explain that if we want to use that term. Before we embark on such a massive documentation change, I'd like to try to find a less invasive change of terminology, if that exists. Do you see a way to do that? Basically, what this feature offers is a way to produce a summary from messages that are already "summarized" by some criteria. So I'd prefer that our terminology alluded to this aspect rather than to "filtering", because then it would be natural and won't require significant changes in the documentation of what Rmail summary commands do.