--- /dev/null
+Return-Path: <m.walters@qmul.ac.uk>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id ECABB431FBF\r
+ for <notmuch@notmuchmail.org>; Sun, 21 Jul 2013 01:49:43 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -1.098\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5\r
+ tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001,\r
+ NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_MED=-2.3] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id 4nghuZfRbJsn for <notmuch@notmuchmail.org>;\r
+ Sun, 21 Jul 2013 01:49:38 -0700 (PDT)\r
+Received: from mail2.qmul.ac.uk (mail2.qmul.ac.uk [138.37.6.6])\r
+ (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 32AAD431FB6\r
+ for <notmuch@notmuchmail.org>; Sun, 21 Jul 2013 01:49:38 -0700 (PDT)\r
+Received: from smtp.qmul.ac.uk ([138.37.6.40])\r
+ by mail2.qmul.ac.uk with esmtp (Exim 4.71)\r
+ (envelope-from <m.walters@qmul.ac.uk>)\r
+ id 1V0pKi-0000QS-FU; Sun, 21 Jul 2013 09:49:36 +0100\r
+Received: from 93-97-24-31.zone5.bethere.co.uk ([93.97.24.31] helo=localhost)\r
+ by smtp.qmul.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.71)\r
+ (envelope-from <m.walters@qmul.ac.uk>)\r
+ id 1V0pKi-0004V3-4w; Sun, 21 Jul 2013 09:49:36 +0100\r
+From: Mark Walters <markwalters1009@gmail.com>\r
+To: Vladimir Marek <Vladimir.Marek@Oracle.COM>, notmuch@notmuchmail.org\r
+Subject: Re: how to work with entire threads\r
+In-Reply-To: <20130709122200.GA11501@virt.cz.oracle.com>\r
+References: <20130709122200.GA11501@virt.cz.oracle.com>\r
+User-Agent: Notmuch/0.15.2+192~g8222af3 (http://notmuchmail.org) Emacs/23.4.1\r
+ (i486-pc-linux-gnu)\r
+Date: Sun, 21 Jul 2013 09:49:35 +0100\r
+Message-ID: <87bo5w8fhc.fsf@qmul.ac.uk>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-Sender-Host-Address: 93.97.24.31\r
+X-QM-SPAM-Info: Sender has good ham record. :)\r
+X-QM-Body-MD5: d6edd6da35e110395b9db86f3666b79f (of first 20000 bytes)\r
+X-SpamAssassin-Score: 0.0\r
+X-SpamAssassin-SpamBar: /\r
+X-SpamAssassin-Report: The QM spam filters have analysed this message to\r
+ determine if it is\r
+ spam. We require at least 5.0 points to mark a message as spam.\r
+ This message scored 0.0 points. Summary of the scoring: \r
+ * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail\r
+ provider * (markwalters1009[at]gmail.com)\r
+ * 0.0 AWL AWL: From: address is in the auto white-list\r
+X-QM-Scan-Virus: ClamAV says the message is clean\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sun, 21 Jul 2013 08:49:44 -0000\r
+\r
+\r
+Hi\r
+Vladimir Marek <Vladimir.Marek@Oracle.COM> writes:\r
+\r
+> Hi,\r
+>\r
+> I would like to create the following process:\r
+>\r
+> 1) if I tag any message with the keyword 'kill', it means that I don't\r
+> want to see any message from whole thread in my inbox\r
+>\r
+> At the moment I do something like\r
+>\r
+> THREADS=$(notmuch search --output=threads tag:kill)\r
+> [ -z "$THREADS" ] || notmuch tag -unread -- '(' $THREADS ')'\r
+>\r
+> 2) if there is such a 'killed' thread and it won't receive message for\r
+> 30 days, I want to remove the kill tag from the thread\r
+>\r
+> That I achieved by something like\r
+>\r
+> N=notmuch\r
+> KILL=$( $N search --output=threads tag:kill ) \r
+> if [ -n "$KILL" ]; then\r
+> # Then find threads which contain messages younger than 30 days\r
+> KILL_RECENT=$( $N search --output=threads '(' $KILL ')' and date:30days.. )\r
+> KILL_RECENT=${KILL_RECENT:-'*'}\r
+> # Then find 'kill' threads not matching those recent\r
+> KILL_COUNT=$( $N count --output=threads '(' $KILL ')' and not '(' $KILL_RECENT ')' )\r
+> if [ $KILL_COUNT -gt 0 ]; then\r
+> echo "Threads to remove 'kill': $KILL"\r
+> $N tag -kill -- $( $N search --output=threads '(' $KILL ')' and not '(' $KILL_RECENT ')' )\r
+> fi\r
+> fi\r
+>\r
+>\r
+>\r
+> I was thinking if it could not be simplified. Without knowing anything about\r
+> notmuch or xapian internals, it seems that it would be handy to change the\r
+> search pattern to return threads. My two previous examples would then read like\r
+>\r
+> 1) notmuch tag -unread -- 'threads(tag:kill)'\r
+> and\r
+> 2) notmuch tag -kill -- 'threads(tag:kill)' and not 'threads(date:30days..)'\r
+>\r
+> Given that this would be possible in the first place, wouldn't it be a nice\r
+> addition to notmuch?\r
+\r
+Some form of general thread based search would definitely be a nice\r
+addition. This seems to be non-trivial as we would need to parse the\r
+query ourselves rather than leaving that to xapian.\r
+\r
+However, I think thread bases tagging would be quite easy:\r
+\r
+eg\r
+\r
+notmuch tag --thread +/-tags <search-term>\r
+\r
+to tag all messages in all threads that contain a message match the\r
+search terms. Your first case would become notmuch tag --thread\r
+-unread tag:kill but your second case would still not be directly\r
+possible.\r
+\r
+Would this be a useful addition by itself?\r
+\r
+Best wishes\r
+\r
+Mark\r
+\r
projects / notmuch-archives.git / commitdiff