1 Return-Path: <five9a2@gmail.com>
\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 0CD29431FBC
\r
6 for <notmuch@notmuchmail.org>; Sun, 22 Nov 2009 13:26:04 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
8 Received: from olra.theworths.org ([127.0.0.1])
\r
9 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
10 with ESMTP id GmCXGPkD46xC for <notmuch@notmuchmail.org>;
\r
11 Sun, 22 Nov 2009 13:26:03 -0800 (PST)
\r
12 Received: from mail-bw0-f224.google.com (mail-bw0-f224.google.com
\r
14 by olra.theworths.org (Postfix) with ESMTP id 0E391431FAE
\r
15 for <notmuch@notmuchmail.org>; Sun, 22 Nov 2009 13:26:02 -0800 (PST)
\r
16 Received: by bwz24 with SMTP id 24so3514164bwz.30
\r
17 for <notmuch@notmuchmail.org>; Sun, 22 Nov 2009 13:26:02 -0800 (PST)
\r
18 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
\r
19 h=domainkey-signature:received:received:sender:from:to:subject:date
\r
20 :message-id:mime-version:content-type;
\r
21 bh=T9mmwMIomcZBJeF6aUkfTAqMt/Gx00wRsrX+IlUKGWY=;
\r
22 b=TXCI5+Epzh/y6F4Nm1JCgJLY1fTXXqTA2XYe13kfyWBnL49fC1inGrC3wFq8yDAXnS
\r
23 NtILLxla/sJw3+YAqObjOICxch5viLvo0x4HSv5jQ3shXs6B61R4/Z4Iz/lDPNLF4RSE
\r
24 gwQJH1vxzIFxZQ7doKRKwOsuTvotneJ5J53ks=
\r
25 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
\r
26 h=sender:from:to:subject:date:message-id:mime-version:content-type;
\r
27 b=XCTheAy+ErfMPZQ2p7cbRuYFNBIjpXJioHJCs4A5owYONgJyrnyeuWhXjXJ4Bw8Vtr
\r
28 NjY1gbr5dyRYgx2W6VrteFZUsRNI88GjmRcVHvc3pgFpUATKCQpjbYrqY59JUm2XFZJQ
\r
29 lUlxbvcgw+k2Fz1Egq7We4lELbMpGfwfGw6hk=
\r
30 Received: by 10.204.34.3 with SMTP id j3mr3922509bkd.23.1258925161989;
\r
31 Sun, 22 Nov 2009 13:26:01 -0800 (PST)
\r
32 Received: from kunyang (vawpc43.ethz.ch [129.132.59.11])
\r
33 by mx.google.com with ESMTPS id y15sm4767743fkd.56.2009.11.22.13.26.00
\r
34 (version=TLSv1/SSLv3 cipher=RC4-MD5);
\r
35 Sun, 22 Nov 2009 13:26:01 -0800 (PST)
\r
36 Sender: Jed Brown <five9a2@gmail.com>
\r
37 From: Jed Brown <jed@59A2.org>
\r
38 To: notmuch@notmuchmail.org
\r
39 Date: Sun, 22 Nov 2009 22:26:31 +0100
\r
40 Message-ID: <87y6ly45fc.fsf@59A2.org>
\r
42 Content-Type: text/plain; charset=us-ascii
\r
43 Subject: [notmuch] [RFC] Precedence of OR and AND
\r
44 X-BeenThere: notmuch@notmuchmail.org
\r
45 X-Mailman-Version: 2.1.12
\r
47 List-Id: "Use and development of the notmuch mail system."
\r
48 <notmuch.notmuchmail.org>
\r
49 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
50 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
51 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
52 List-Post: <mailto:notmuch@notmuchmail.org>
\r
53 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
54 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
55 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
56 X-List-Received-Date: Sun, 22 Nov 2009 21:26:04 -0000
\r
58 Currently OR binds more weakly than AND, which is natural in most
\r
59 contexts, but I think it is rarely desirably for this sort of search.
\r
60 Suppose I am in looking at my inbox and decide to filter by
\r
64 Notmuch makes the query
\r
66 tag:inbox AND term1 OR term2
\r
70 (tag:inbox AND term1) OR term2
\r
72 and not at all what I wanted. Adding the necessary parentheses to
\r
73 notmuch-search-filter is trivial but it requires more parentheses for
\r
74 the overwhelming majority of searches that I think are more common.
\r
76 Are most searches indeed closer to conjunctive form?
\r
78 Should OR bind tighter than AND?
\r