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