From: "Antoine Beaupré" <anarcat@orangeseeds.org>
To: Jameson Graef Rollins <jrollins@caltech.edu>,
Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Teemu Likonen <tlikonen@iki.fi>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: proposing "notmuch purge"
Date: Tue, 14 Jan 2020 15:03:29 -0500 [thread overview]
Message-ID: <87d0blyfe6.fsf@curie.anarc.at> (raw)
In-Reply-To: <87wo9tdd8n.fsf@caltech.edu>
On 2020-01-14 11:55:36, Jameson Graef Rollins wrote:
> On Tue, Jan 14 2020, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
>>> I think that the "SEARCH-TERMS" part should be configurable, not
>>> hard-coded. A user could have setting like
>>> "search.purge_tags=deleted;spam" and that would lead to search terms
>>> "tag:deleted OR tag:spam" in the purge operation.
>>
>> I want the user to be able to run "notmuch purge", with no arguments, to
>> "Do What I Mean"™
>>
>> I also want the "purge" subcommand to have its own configuration
>> space -- it's *not* a specialized form of "search".
>
> Honestly I don't see the point of any user configuration here. Seems
> likely to only add confusion and possibly improperly deleted messages,
> which would be very bad.
>
> Just use the "deleted" tag only. It's already being used in multiple
> place to mean that the message should be deleted.
Agreed. If you want to delete messages matching an another tag, you just
run:
notmuch tag +deleted tag:another
notmuch purge
Composability wins over configurability in this case. :)
A.
--
Le péché est né avant la vertu, comme le moteur avant le frein.
- Jean-Paul Sartre
next prev parent reply other threads:[~2020-01-14 20:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 22:28 proposing "notmuch purge" Daniel Kahn Gillmor
2020-01-13 22:33 ` Antoine Beaupré
2020-01-14 5:01 ` Teemu Likonen
2020-01-14 5:36 ` Teemu Likonen
2020-01-14 19:23 ` Daniel Kahn Gillmor
2020-01-14 19:55 ` Jameson Graef Rollins
2020-01-14 20:03 ` Antoine Beaupré [this message]
2020-01-14 22:25 ` Daniel Kahn Gillmor
2020-01-15 5:36 ` Teemu Likonen
2020-01-15 9:58 ` Örjan Ekeberg
2020-01-14 22:48 ` Ryan Tate
2020-01-14 23:08 ` Jameson Graef Rollins
2020-01-15 1:43 ` Antoine Beaupré
2020-01-14 22:59 ` Brian May
2020-01-14 23:24 ` Daniel Kahn Gillmor
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0blyfe6.fsf@curie.anarc.at \
--to=anarcat@orangeseeds.org \
--cc=dkg@fifthhorseman.net \
--cc=jrollins@caltech.edu \
--cc=notmuch@notmuchmail.org \
--cc=tlikonen@iki.fi \
/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://yhetil.org/notmuch.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).