Content-Type: multipart/signed; protocol="application/pgp-signature";
	micalg="pgp-sha1"; boundary="===============6462341303496013660=="
MIME-Version: 1.0
Content-Disposition: inline
From: Patrick Totzke <patricktotzke@gmail.com>
User-Agent: alot/0.3.2+
To: David Froger <david.froger@gmail.com>,  notmuch@notmuchmail.org
References: <20120812152258.GA32178@hili.localdomain>
	<20120812144023.GC29680@david-desktop.localdomain>
	<20120813003735.GA20739@hili.localdomain>
	<20120812175343.GA32257@david-desktop.localdomain>
In-Reply-To: <20120812175343.GA32257@david-desktop.localdomain>
Message-ID: <20120812203339.14936.26407@brick.lan>
Subject: Re: [announce] Bower 0.4
Date: Sun, 12 Aug 2012 21:33:39 +0100
Precedence: list

--===============6462341303496013660==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Quoting David Froger (2012-08-12 16:53:43)
> > > 3. Would it be possible to have the feature 'kill a thread' like Sup =
have? (see
> > > http://sup.rubyforge.org/README.txt).
> > =

> > I haven't needed such a feature so I don't have a clear idea how it
> > should work.  There are some patches/ideas about muting threads using
> > notmuch generally around here.  I guess the simplest thing to do is hide
> > a thread if it has a certain tag, e.g. "muted" as suggested by notmuch
> > TODO file, unless you search for it explicitly.
> I  like this  solution,  I will  use it (adding 'and not tag:mutted' at t=
he end of my search).
> When  I'm not  interessed with  a long discussion on a mailling list,  I =
like to  be able to 'kill'
> the thread so it does not reappear with every new mail.

I'm not sure if this actually solves your problem, because
notmuch's search is message, not thread based:
If you search for threads that match "is:inbox and not is:muted", you will =
see threads
that contain messages which are tagged with "inbox" and not with "muted".
This means if you just tag one (or all) msg in a thread "muted" and there i=
s a new response,
this thread will contain such a matching message again and show up in your =
result list.

To make this work, you need to set up your tagging script (that you run aft=
er 'notmuch new')
so that it updates those new messages accordingly. If a msg belongs to a th=
read that has =

muted messages, also tag the new one muted.
I can pretty much recommend Justus' tagging script afew: https://github.com=
/teythoon/afew
One of the filters that it supports out of the box is exactly the "kill thr=
eads" function
you want.

HTH,
/p

--===============6462341303496013660==
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Description: signature
Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEABECAAYFAlAoEyMACgkQlDQDZ9fWxarU+gCfXcwPmiuZrZNoSpcY8LQIqp/h
SEYAoJTRXQmvs6AAgMIlXvcE0VttzG5r
=shh8
-----END PGP SIGNATURE-----

--===============6462341303496013660==--