From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 62DB9431FB6 for ; Mon, 13 Aug 2012 21:59:46 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.799 X-Spam-Level: X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IeaZqv9tIpPk for ; Mon, 13 Aug 2012 21:59:45 -0700 (PDT) Received: from mail-we0-f181.google.com (mail-we0-f181.google.com [74.125.82.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 8D693431FAE for ; Mon, 13 Aug 2012 21:59:45 -0700 (PDT) Received: by weyt57 with SMTP id t57so3445443wey.26 for ; Mon, 13 Aug 2012 21:59:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:message-id:from:to:subject:in-reply-to:references:mime-version :content-type:content-disposition:content-transfer-encoding; bh=mC4jivNHzA4QJU9SGk14bRyRs5Xn2Bhvxbm0LFPdIJo=; b=Fkyeetj/bTuDcncW0XLYXHKdJwKpzyG/wYWXhBAIotBvXQP8c47z6Km2aHZTKEGd+7 u44JADhfKC53EwMItP3L15avjEFPAMP4z3UrD33if6twkEg+Id7NxgZ684k6QTGNFWj5 BLmRq3nmQD47mgrkuATsqgXKH7lR7L+RtpCmRCrjeX5JY//AjLK9IByOB9fOSIO2sDt1 CkIA//C+zMNpQ4HV6+gz8ud5ewNlDaEtjaGYf4BCtUtWVG3f3OR5re3A3erDxvq6wbCk oH1tNzgzFVUx2jNV0+B2GNB9GDpwzr9mxeYQTPKUImLbociXpNNyH4uwaVfu6+UXHyH4 TIuA== Received: by 10.180.99.102 with SMTP id ep6mr4610057wib.19.1344920382871; Mon, 13 Aug 2012 21:59:42 -0700 (PDT) Received: from localhost (253.53.100.84.rev.sfr.net. [84.100.53.253]) by mx.google.com with ESMTPS id t7sm29623657wix.6.2012.08.13.21.59.40 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 13 Aug 2012 21:59:41 -0700 (PDT) Date: Tue, 14 Aug 2012 06:59:39 +0200 Message-ID: <20120814065939.GA31346@david-desktop.localdomain> From: David Froger To: notmuch@notmuchmail.org Subject: Re: [announce] Bower 0.4 In-Reply-To: <20120812203339.14936.26407@brick.lan> References: <20120812152258.GA32178@hili.localdomain> <20120812144023.GC29680@david-desktop.localdomain> <20120813003735.GA20739@hili.localdomain> <20120812175343.GA32257@david-desktop.localdomain> <20120812203339.14936.26407@brick.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2012 04:59:46 -0000 On Sun, 12 Aug 2012 21:33:39 +0100, Patrick Totzke wrote: > 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 the 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 is a new response, > this thread will contain such a matching message again and show up in your result list. Thanks for the clarification, it's very helpfull! > > To make this work, you need to set up your tagging script (that you run after 'notmuch new') > so that it updates those new messages accordingly. If a msg belongs to a thread 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 threads" function > you want. Thanks, this script looks very cool and I think I will replace mine with it (I should have visited (http://notmuchmail.org/initial_tagging/ ...). You're right, the filter I'm interessed is in in aftew/filters/KillThreadsFilter.py, and do this: for all email M that does not have tag 'killed': I = thread Id of the email M if there are emails that have thread id I and the 'killed' tag: apply 'killed' tag on email E Thanks again for all the help.