From: Carl Worth <cworth@cworth.org>
To: Jameson Rollins <jrollins@finestructure.net>, racin@free.fr,
	Sebastian Spaeth <Sebastian@SSpaeth.de>
In-Reply-To: <87tyt61mrl.fsf@servo.finestructure.net>
References:
 <1161359196.2247691263984967906.JavaMail.root@zimbra1-e1.priv.proxad.net>
	<87sk8qwjlt.fsf@yoom.home.cworth.org>
	<87tyt61mrl.fsf@servo.finestructure.net>
Date: Wed, 24 Feb 2010 11:28:29 -0800
Message-ID: <87ljeiwi02.fsf@yoom.home.cworth.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: [notmuch] [PATCH] add notmuch-show-delete keybinding 'd'
Precedence: list

--=-=-=
Content-Transfer-Encoding: quoted-printable

On Wed, 24 Feb 2010 14:01:18 -0500, Jameson Rollins <jrollins@finestructure=
.net> wrote:
> > 2. It removes the "inbox" and "unread" tags while adding the tag to
> >    indicate deletion.
>=20
> Hey, Carl.  Why is this last point important?

I guess I was imagining the case of running "notmuch search tag:inbox"
at the command-line. That output will get out of hand fairly quickly if
it includes all deleted messages back to the beginning of time, (or as
far back as the window of actually deleting files from the
mailstore[*]).

But you're right that tags should really be handled orthogonally. Maybe
what we want is lower-level support for the "deleted" tag? Other than
just the high-level emacs interface?

That could put *more* direct interpretation of specific tags in the low
levels. And this is the opposite direction of where we've been going (or
talking about at least). We've currently got "inbox" and "unread" inside
the low levels and there's been talking or removing those, switching to
just "new" or making it all configurable.

I do know that I also want to have low-level support for "muted" (aka
"killed" threads). For that I want an --exclude option to notmuch search
that would look something like this:

notmuch search --exclude=3D"<negative-search-terms>" <positive-search-terms>

Where the result would be the set difference of the threads matched by
the two sets of search terms. Perhaps with something like that in place
all we'd want in addition would be a configuration option to add
=2D-exclude=3Dtag:muted by default. And if we go that route, perhaps we
could have an option for an implicit "and not tag:deleted" for the
search terms as well.

I do worry about making the command-line tool hard to use without a
configuration file, but it also seems very appealing to keep the lowest
levels very general to allow people to experiment with whatever they
want on top.

=2DCarl

[*] My eventual plan for detected spam and manually deleted messages is
to keep them in the mail store so they are searchable for some time (a
month or two) and then deleting them after that (with something like a
cron job using a convenient --before=3D"2 months ago" syntax to a notmuch
search command).

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFLhX3d6JDdNq8qSWgRAp7eAJ9KPLxu4Gfiij5LzL3jXuf4hvxkZwCfUKE1
U5qf6sS+SX+D86MEgFd+mgg=
=mtan
-----END PGP SIGNATURE-----
--=-=-=--