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 ACC22431FB6
\r
6 for <notmuch@notmuchmail.org>; Wed, 30 May 2012 00:49:34 -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 0eX3sFUf2ZWX for <notmuch@notmuchmail.org>;
\r
17 Wed, 30 May 2012 00:49:33 -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 14C57431FAF
\r
22 for <notmuch@notmuchmail.org>; Wed, 30 May 2012 00:49:33 -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 1SZdeq-0007dR-SF; Wed, 30 May 2012 08:49:29 +0100
\r
27 Received: from 94-192-233-223.zone6.bethere.co.uk ([94.192.233.223]
\r
29 by smtp.qmul.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69)
\r
30 (envelope-from <m.walters@qmul.ac.uk>)
\r
31 id 1SZdeq-00033C-JI; Wed, 30 May 2012 08:49:28 +0100
\r
32 From: Mark Walters <markwalters1009@gmail.com>
\r
33 To: Peter Wang <novalazy@gmail.com>, notmuch@notmuchmail.org
\r
34 Subject: Re: search summary and exclusions
\r
35 In-Reply-To: <20120530130733.GC2332@hili.localdomain>
\r
36 References: <20120529000012.GF2331@hili.localdomain>
\r
37 <87mx4sp79z.fsf@servo.finestructure.net>
\r
38 <20120529140107.GE2347@hili.localdomain>
\r
39 <87fwajnibz.fsf@servo.finestructure.net>
\r
40 <20120530130733.GC2332@hili.localdomain>
\r
41 User-Agent: Notmuch/0.13+55~g992aa73 (http://notmuchmail.org) Emacs/23.3.1
\r
42 (x86_64-pc-linux-gnu)
\r
43 Date: Wed, 30 May 2012 08:49:31 +0100
\r
44 Message-ID: <878vgam7lg.fsf@qmul.ac.uk>
\r
46 Content-Type: text/plain; charset=us-ascii
\r
47 X-Sender-Host-Address: 94.192.233.223
\r
48 X-QM-SPAM-Info: Sender has good ham record. :)
\r
49 X-QM-Body-MD5: 26f30eab317eac93c3b77d83ce719d55 (of first 20000 bytes)
\r
50 X-SpamAssassin-Score: -1.8
\r
51 X-SpamAssassin-SpamBar: -
\r
52 X-SpamAssassin-Report: The QM spam filters have analysed this message to
\r
54 spam. We require at least 5.0 points to mark a message as spam.
\r
55 This message scored -1.8 points.
\r
56 Summary of the scoring:
\r
57 * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/,
\r
59 * [138.37.6.40 listed in list.dnswl.org]
\r
60 * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail
\r
61 provider * (markwalters1009[at]gmail.com)
\r
62 * -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
\r
64 * 0.5 AWL AWL: From: address is in the auto white-list
\r
65 X-QM-Scan-Virus: ClamAV says the message is clean
\r
66 X-BeenThere: notmuch@notmuchmail.org
\r
67 X-Mailman-Version: 2.1.13
\r
69 List-Id: "Use and development of the notmuch mail system."
\r
70 <notmuch.notmuchmail.org>
\r
71 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
72 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
73 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
74 List-Post: <mailto:notmuch@notmuchmail.org>
\r
75 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
76 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
77 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
78 X-List-Received-Date: Wed, 30 May 2012 07:49:34 -0000
\r
81 On Wed, 30 May 2012, Peter Wang <novalazy@gmail.com> wrote:
\r
82 > On Tue, 29 May 2012 08:00:00 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
\r
83 >> On Mon, May 28 2012, Peter Wang <novalazy@gmail.com> wrote:
\r
84 >> > % ./notmuch search --format=json --exclude=true -- thread:0000000000009598 tag:unread
\r
85 >> > [{"thread": "0000000000009598",
\r
86 >> > "timestamp": 1338231998,
\r
87 >> > "date_relative": "Today 05:06",
\r
90 >> > "authors": "Mark Walters| Peter Wang",
\r
91 >> > "subject": "[PATCH v6 3/6] cli: make --entire-thread=false work for format=json.",
\r
92 >> > "tags": ["deleted", "draft", "replied", "sent", "unread"]}]
\r
94 >> > Here is a thread I participated in. From this, my MUA displays "1/15",
\r
95 >> > suggesting that there is 1 unread message out of a total of 15. But
\r
96 >> > upon opening the thread, there are only 11 messages visible: 4 were
\r
97 >> > drafts (possibly deleted) which have been excluded. To the user, it
\r
98 >> > looks like some messages went missing.
\r
100 >> > Therefore I would like search --output=summary --exclude=true
\r
101 >> > to report the total number of non-excluded messages. It doesn't need to
\r
102 >> > be via the "total" field; a new field would be fine.
\r
104 >> What you have pasted above is --output=json, not --output=summary. The
\r
105 >> formats are quite different. What are you asking for a change in?
\r
107 > --output=summary is the default. --format=json only changes the
\r
110 > % ./notmuch search --output=summary --exclude=true -- thread:0000000000009598 tag:unread
\r
111 > thread:0000000000009598 Yest. 05:06 [1/15] Mark Walters| Peter Wang; [PATCH v6 3/6] cli: make --entire-thread=false work for format=json. (deleted draft replied sent unread)
\r
113 >> But regardless, I don't think I would like to see the changes you
\r
114 >> suggest. I would like for the thread total to list the total number of
\r
115 >> messages in the thread, regardless whether they're excluded or not.
\r
116 >> Same for the tags. I think I want to continue to see if excluded
\r
117 >> messages are in a returned thread. The desire to hide the excluded
\r
118 >> messages in the output is why they're marked as hidden/not visible.
\r
120 >> Think about the excludes as acting on the search itself, and less on the
\r
121 >> output. We exclude messages from search, but if they show up in a
\r
122 >> returned thread we at least acknowledge that they're there.
\r
124 > Understood; it's a two-phase process, and I wasn't making the
\r
125 > distinction. If it is the expected and useful behaviour, so be it.
\r
127 > Maybe there is room for another keyword under --exclude?
\r
129 Yes that might be the best way to go. Something like --exclude=all and
\r
130 then excluded messages never appear anywhere?
\r
132 I think it should be easy: I will try to send a patch tonight.
\r