From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, andrea.monaco@autistici.org, emacs-devel@gnu.org
Subject: Re: [PATCH v3] Allow applying filters to summary consecutively
Date: Thu, 10 Nov 2022 09:53:08 +0100 [thread overview]
Message-ID: <8735arfax7.fsf@gmail.com> (raw)
In-Reply-To: <83r0ybs07r.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 10 Nov 2022 10:06:00 +0200")
>>>>> On Thu, 10 Nov 2022 10:06:00 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> From: Richard Stallman <rms@gnu.org>
>> Cc: eliz@gnu.org, rpluim@gmail.com, emacs-devel@gnu.org
>> Date: Wed, 09 Nov 2022 23:04:02 -0500
>>
>> Does it mean "using one summary filtering cpmmand when a filtered
>> summary already exists"? That is the meaning I would expect in this
>> case. But if so, "consecutive commands" is not the way to say it.
Eli> Your guess is correct. I was struggling with finding a good
Eli> description for this. What would you suggest as a good wording?
I think we can keep it down to one sentence if we follow the 'describe
what it affects' guidance for docstrings, which allows dropping the
'if non-nil' bit. So something like:
"Whether summary filtering commands apply to an existing summary.
If nil, a new filtered summary is created, if non-nil, subsequent
filtering commands apply to an existing filtered summary. This allows
the user to apply one filter after the other and keep narrowing the
results."
(the name of the option may need to change)
Robert
--
next prev parent reply other threads:[~2022-11-10 8:53 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 18:31 Summary by thread in rmail Andrea Monaco
2022-10-05 18:49 ` Eli Zaretskii
2022-10-05 23:40 ` Emanuel Berg
2022-10-06 22:04 ` Richard Stallman
2022-10-07 10:17 ` Andrea Monaco
2022-10-07 11:24 ` Emanuel Berg
2022-10-09 20:33 ` [PATCH] Allow applying filters to summary consecutively (was: Summary by thread in rmail) Andrea Monaco
2022-10-10 7:31 ` Eli Zaretskii
2022-10-10 8:38 ` Andrea Monaco
2022-10-10 8:57 ` Eli Zaretskii
2022-10-11 7:16 ` [PATCH v2] " Andrea Monaco
2022-10-11 8:13 ` [PATCH v2] Allow applying filters to summary consecutively Robert Pluim
2022-10-12 9:35 ` Andrea Monaco
2022-10-12 11:03 ` Robert Pluim
2022-10-12 12:56 ` Eli Zaretskii
2022-10-12 18:13 ` Andrea Monaco
2022-10-12 18:22 ` Eli Zaretskii
2022-10-12 22:02 ` Richard Stallman
2022-10-19 14:23 ` [PATCH v3] " Andrea Monaco
2022-10-19 14:55 ` Robert Pluim
2022-10-20 15:45 ` Andrea Monaco
2022-10-20 16:02 ` Robert Pluim
2022-10-20 19:00 ` Andrea Monaco
2022-10-21 19:42 ` Richard Stallman
2022-10-21 19:38 ` Richard Stallman
2022-10-27 14:27 ` Eli Zaretskii
2022-10-27 15:22 ` Andrea Monaco
2022-10-28 13:26 ` Andrea Monaco
2022-11-06 7:34 ` Eli Zaretskii
2022-11-07 14:13 ` Andrea Monaco
2022-11-08 5:02 ` Richard Stallman
2022-11-08 8:04 ` Andrea Monaco
2022-11-14 3:13 ` Richard Stallman
2022-11-10 4:04 ` Richard Stallman
2022-11-10 8:06 ` Eli Zaretskii
2022-11-10 8:53 ` Robert Pluim [this message]
2022-11-11 4:36 ` Richard Stallman
2022-11-11 8:06 ` Eli Zaretskii
2022-11-11 14:59 ` Juanma Barranquero
2022-11-11 17:23 ` Eli Zaretskii
2022-11-11 17:32 ` [External] : " Drew Adams
2022-11-11 18:00 ` Gregory Heytings
2022-11-11 18:19 ` Eli Zaretskii
2022-11-11 18:52 ` Gregory Heytings
2022-11-11 18:54 ` Gregory Heytings
2022-11-11 19:34 ` Eli Zaretskii
2022-11-11 19:33 ` Eli Zaretskii
2022-11-11 20:50 ` Gregory Heytings
2022-11-12 3:37 ` Richard Stallman
2022-11-12 7:52 ` Eli Zaretskii
2022-11-12 6:57 ` Eli Zaretskii
2022-11-12 16:30 ` Gregory Heytings
2022-11-12 17:44 ` Andrea Monaco
2022-11-12 18:13 ` Gregory Heytings
2022-11-14 3:13 ` Richard Stallman
2022-11-14 8:39 ` Gregory Heytings
2022-11-15 4:18 ` Richard Stallman
2022-11-15 9:56 ` Gregory Heytings
2022-11-16 3:15 ` Richard Stallman
2022-11-16 3:15 ` Richard Stallman
2022-11-24 18:25 ` Andrea Monaco
2022-11-28 21:38 ` Richard Stallman
2022-11-15 17:00 ` [External] : " Drew Adams
2022-11-14 3:13 ` Richard Stallman
2022-11-15 9:35 ` Gregory Heytings
2022-11-16 3:15 ` Richard Stallman
2022-11-19 14:47 ` Gregory Heytings
2022-11-20 17:37 ` Richard Stallman
2022-11-20 19:36 ` Gregory Heytings
2022-11-22 12:14 ` Richard Stallman
2022-11-22 12:58 ` Gregory Heytings
2022-11-28 21:38 ` Richard Stallman
2022-11-23 20:57 ` chad
2022-11-24 6:39 ` Eli Zaretskii
2022-11-28 21:38 ` Richard Stallman
2022-11-26 0:51 ` Richard Stallman
2022-11-11 18:22 ` [External] : " Drew Adams
2022-11-12 3:35 ` Richard Stallman
2022-11-12 7:47 ` Eli Zaretskii
2022-11-14 3:13 ` Richard Stallman
2022-11-17 13:34 ` Eli Zaretskii
2022-10-27 13:58 ` [PATCH v2] Allow applying filters to summary consecutively (was: Summary by thread in rmail) Eli Zaretskii
2022-10-10 22:03 ` [PATCH] " Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735arfax7.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=andrea.monaco@autistici.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).