1 Return-Path: <jrollins@finestructure.net>
\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 1A7E6431E82
\r
6 for <notmuch@notmuchmail.org>; Wed, 15 Feb 2012 14:16:25 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-2.29 tagged_above=-999 required=5
\r
12 tests=[RCVD_IN_DNSWL_MED=-2.3, T_MIME_NO_TEXT=0.01] autolearn=disabled
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id Nxdm0KQLPXyc for <notmuch@notmuchmail.org>;
\r
16 Wed, 15 Feb 2012 14:16:23 -0800 (PST)
\r
17 Received: from outgoing-mail.its.caltech.edu (outgoing-mail.its.caltech.edu
\r
19 by olra.theworths.org (Postfix) with ESMTP id EB2A8431E62
\r
20 for <notmuch@notmuchmail.org>; Wed, 15 Feb 2012 14:16:22 -0800 (PST)
\r
21 Received: from fire-doxen.imss.caltech.edu (localhost [127.0.0.1])
\r
22 by fire-doxen-postvirus (Postfix) with ESMTP id 29EBB328064;
\r
23 Wed, 15 Feb 2012 14:16:22 -0800 (PST)
\r
24 X-Spam-Scanned: at Caltech-IMSS on fire-doxen by amavisd-new
\r
25 Received: from finestructure.net (DHCP-123-180.caltech.edu [131.215.123.180])
\r
26 (Authenticated sender: jrollins)
\r
27 by fire-doxen-submit (Postfix) with ESMTP id 5100F2E50D9A;
\r
28 Wed, 15 Feb 2012 14:16:19 -0800 (PST)
\r
29 Received: by finestructure.net (Postfix, from userid 1000)
\r
30 id F20A84D3; Wed, 15 Feb 2012 14:16:18 -0800 (PST)
\r
31 From: Jameson Graef Rollins <jrollins@finestructure.net>
\r
32 To: Mark Walters <markwalters1009@gmail.com>, notmuch@notmuchmail.org
\r
33 Subject: Re: [RFC PATCH v5 00/11] Add NOTMUCH_MESSAGE_FLAG_EXCLUDED flag
\r
34 In-Reply-To: <8739aber9o.fsf@qmul.ac.uk>
\r
35 References: <1329296619-7463-1-git-send-email-markwalters1009@gmail.com>
\r
36 <8739acrnu7.fsf@servo.finestructure.net>
\r
37 <8739aber9o.fsf@qmul.ac.uk>
\r
38 User-Agent: Notmuch/0.11.1+192~g2bb5859 (http://notmuchmail.org) Emacs/23.3.1
\r
39 (x86_64-pc-linux-gnu)
\r
40 Date: Wed, 15 Feb 2012 14:16:16 -0800
\r
41 Message-ID: <874nurrbdb.fsf@servo.finestructure.net>
\r
43 Content-Type: multipart/signed; boundary="=-=-=";
\r
44 micalg=pgp-sha256; protocol="application/pgp-signature"
\r
45 X-BeenThere: notmuch@notmuchmail.org
\r
46 X-Mailman-Version: 2.1.13
\r
48 List-Id: "Use and development of the notmuch mail system."
\r
49 <notmuch.notmuchmail.org>
\r
50 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
51 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
52 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
53 List-Post: <mailto:notmuch@notmuchmail.org>
\r
54 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
55 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
56 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
57 X-List-Received-Date: Wed, 15 Feb 2012 22:16:25 -0000
\r
60 Content-Transfer-Encoding: quoted-printable
\r
62 On Wed, 15 Feb 2012 21:11:15 +0000, Mark Walters <markwalters1009@gmail.com=
\r
64 > I think the difficulty is that there are lots of annoying corner cases,
\r
65 > but if there is a simpler solution that would be great!
\r
69 > 1) What should notmuch show id:deleted-message-id do?=20
\r
71 > It could return the thread containing the deleted message. If it does
\r
72 > return a thread what subject does it assign it? Possibly it could
\r
73 > return no messages and the caller would have to call it again with
\r
76 "notmuch show id:<excluded-id>" should always return the message
\r
77 matching id:<excluded-id> with match=3Dtrue. In fact, any search that
\r
78 references a specific id: should always process the message as if there
\r
79 were no excludes at all.
\r
81 Excluded messages are not directly accessible at the moment, which is
\r
82 definitely a bug. Adding the --no-excludes option will help, but I
\r
83 still think we should just implement the behavior I outline above.
\r
85 > 2) Should notmuch search return threads which match but only in excluded
\r
88 > If yes then does it sort it based on match or match-not-excluded? If the
\r
89 > latter what happens to threads with no match-not-excluded messages? If
\r
90 > not then does searching for id:deleted-message return no results? The
\r
91 > caller could try with --no-exclude, but then the caller would end up
\r
92 > returning the deleted message for search id:deleted-message but not for
\r
93 > search id:deleted-message or id:some-other-not-deleted-message.
\r
95 See the point above. If one of the search terms is an id: then that
\r
96 message should be returned matched, as if there were no excludes.
\r
98 I think this is the right solution, for both search and show:
\r
100 =2D excluded messages are just match=3Dfalse
\r
102 =2D searches that reference a specific id: are match=3Dtrue no matter what
\r
103 their exclude status
\r
105 =2D searches that reference an excluded tag are match=3Dtrue
\r
107 As far as I can see this should "just work", without any existing
\r
108 changes to consumers. Anyone see any issues I'm missing?
\r
113 Content-Type: application/pgp-signature
\r
115 -----BEGIN PGP SIGNATURE-----
\r
116 Version: GnuPG v1.4.11 (GNU/Linux)
\r
118 iQIcBAEBCAAGBQJPPC6wAAoJEO00zqvie6q82KAP/iS+8YA2Rg12NNcjQvFLgRMi
\r
119 Uv6Fhd8tcbaRNASitOigUXVutWdzZMxiteOAOxo+4king614l+7dek/Cv0aChozT
\r
120 bZtkhKmIv4jZPuyWm2kOpmULxJY+ehsQ74jmq7UOoxEyZtytEbLI7HSWPCe9LFAX
\r
121 vdq5SC1fTNopxfdxpF9D5XCiIm6/T5gdT/moCa+BuhvFu/qOJ6UA4AZ7CiM9YbBV
\r
122 ndr/fW203wY6CpUdHnI9XXvcQTF03FKrFKkvaSWlHOxlwO+wOxsWf4glEVPMn/4L
\r
123 w9hlu+4qM7LbB7Iolxc0B6UNo8mHZz/XDerC7kaHOSO3H6+xVH40QCR0kgDOnmgM
\r
124 0fGFQs5J6SxSL6DrOnOfqlJrS9g5C44OU0vx+Qa2puX5kA2kSN03PA0VZBkTD7nr
\r
125 Wi6Bwl+4AHREtts8gU3YdBoQoiLAjVRznblIHJN8BlKiQAlTZUbOLDTPVGINdj/J
\r
126 Y+H01tLZkP/jn+XUFghjjFF41r8lLVcqXR/t6v/ySzEplUW5nfLDm540wBCV5jne
\r
127 HyoZCnFdXKTNDxcDls8ru+OzjKcRnf/FGLcPa9aqEaCaWNX+pK02uJwTcBdX9peW
\r
128 L8SHjWjbZ2+jWkxrywzt4DY9ZOPinbDKepj9ek6jzwgpq03TofoK2ZPfnOIuV5hn
\r
129 +RJN/ngKbnT8uOR30EXk
\r
131 -----END PGP SIGNATURE-----
\r