1 Return-Path: <sojkam1@fel.cvut.cz>
\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 7BD84418C34
\r
6 for <notmuch@notmuchmail.org>; Sat, 10 Apr 2010 13:24:08 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5
\r
12 tests=[BAYES_20=-0.001] autolearn=unavailable
\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 sABLMbZmTCxj for <notmuch@notmuchmail.org>;
\r
16 Sat, 10 Apr 2010 13:24:07 -0700 (PDT)
\r
17 Received: from max.feld.cvut.cz (max.feld.cvut.cz [147.32.192.36])
\r
18 by olra.theworths.org (Postfix) with ESMTP id E29B0418C36
\r
19 for <notmuch@notmuchmail.org>; Sat, 10 Apr 2010 13:24:06 -0700 (PDT)
\r
20 Received: from localhost (unknown [192.168.200.4])
\r
21 by max.feld.cvut.cz (Postfix) with ESMTP id 55A7219F33A6;
\r
22 Sat, 10 Apr 2010 22:24:06 +0200 (CEST)
\r
23 X-Virus-Scanned: IMAP AMAVIS
\r
24 Received: from max.feld.cvut.cz ([192.168.200.1])
\r
25 by localhost (styx.feld.cvut.cz [192.168.200.4]) (amavisd-new,
\r
27 with ESMTP id MzSJgW55r9l8; Sat, 10 Apr 2010 22:24:03 +0200 (CEST)
\r
28 Received: from imap.feld.cvut.cz (imap.feld.cvut.cz [147.32.192.34])
\r
29 by max.feld.cvut.cz (Postfix) with ESMTP id B6BF619F3327;
\r
30 Sat, 10 Apr 2010 22:24:03 +0200 (CEST)
\r
31 Received: from wsheee.localdomain (unknown [213.29.198.144])
\r
32 (Authenticated sender: sojkam1)
\r
33 by imap.feld.cvut.cz (Postfix) with ESMTPSA id 33AA8FA003;
\r
34 Sat, 10 Apr 2010 22:24:03 +0200 (CEST)
\r
35 Received: from wsh by wsheee.localdomain with local (Exim 4.69)
\r
36 (envelope-from <sojkam1@fel.cvut.cz>)
\r
37 id 1O0hDm-0001qX-Aa; Sat, 10 Apr 2010 22:24:02 +0200
\r
38 From: Michal Sojka <sojkam1@fel.cvut.cz>
\r
39 To: Mark Anderson <MarkR.Anderson@amd.com>, Carl Worth <cworth@cworth.org>,
\r
40 "notmuch\@notmuchmail.org" <notmuch@notmuchmail.org>
\r
41 Subject: Re: Initial attempt at a "merge window" for notmuch
\r
42 In-Reply-To: <3wdpr282yz2.fsf@testarossa.amd.com>
\r
43 References: <87hbnktx1c.fsf@yoom.home.cworth.org>
\r
44 <87fx34twrj.fsf@yoom.home.cworth.org>
\r
45 <3wdpr282yz2.fsf@testarossa.amd.com>
\r
46 Date: Sat, 10 Apr 2010 22:24:01 +0200
\r
47 Message-ID: <87ochrdpjy.fsf@wsheee.2x.cz>
\r
49 Content-Type: text/plain; charset=us-ascii
\r
50 X-BeenThere: notmuch@notmuchmail.org
\r
51 X-Mailman-Version: 2.1.13
\r
53 List-Id: "Use and development of the notmuch mail system."
\r
54 <notmuch.notmuchmail.org>
\r
55 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
56 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
57 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
58 List-Post: <mailto:notmuch@notmuchmail.org>
\r
59 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
60 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
61 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
62 X-List-Received-Date: Sat, 10 Apr 2010 20:24:08 -0000
\r
64 On Fri, 09 Apr 2010, Mark Anderson wrote:
\r
65 > On Fri, 9 Apr 2010 11:29:20 -0500, Carl Worth <cworth@cworth.org> wrote:
\r
66 > > Of course, it's the same set-theoretic operation I described earlier. I
\r
67 > > want the set of threads having messages matching:
\r
69 > > tag:notmuch and <date-range>
\r
71 > > intersected with the set of threads having messages matching:
\r
73 > > tag:notmuch and not ("merged" or "postponed")
\r
75 > > So I've got uses cases for set-difference and intersection already. Now
\r
76 > > we just need some search syntax to express that.
\r
79 > Can we just start grouping with a set:( ) or { } on the command line?
\r
80 > I'm guessing the parentheses are slightly easier.
\r
82 > set:( tag:notmuch and <date-range> )
\r
84 > set:( tag:notmuch and not (tag:merged or tag:postponed) )
\r
86 If we go in this direction, I think that the syntax should explicitely
\r
87 state the it is the set of threads and not the set of messages. So maybe
\r
90 threads:( ... ) isect threads:( ... )
\r
92 > Just thinking about completeness, I wonder if there are some searches
\r
93 > for threads that aren't currently available.
\r
95 I think that having a way for searching all threads started by a certain
\r
96 person (e.g. project maintainer) would be very useful. For this we may
\r
97 need some search operator for specifying the position of the message in
\r
98 the thread. For example: notmuch search from:cworth and position:first.
\r
100 In id:4b9d4e24.0f67f10a.31e3.ffffadf7@mx.google.com, Sandra asked for
\r
101 something like: notmuch search not threads:( from:me and position:last )
\r