DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=sender:from:to:cc:subject:in-reply-to:references:date:message-id
	:mime-version:content-type;
	b=a8Q8YKz0rA+BUWPH28fi0ESRE72gH5GAYeMCpidmwFxOhVlMcAZFDo+t7ZpMpzqzOl
	e9p99YQV5bDjKRCRnunZiDnm/ojocDfS6+A7dRJEkwIqt28qAEXqLJggr3uacX3UQ2oS
	PmkIEUY2dHPOLGnFj41MZrInStYLgw8hgUFIA=
Sender: Jed Brown <five9a2@gmail.com>
From: Jed Brown <jed@59A2.org>
To: Bart Trojanowski <bart@jukie.net>
In-Reply-To: <20091122213649.GJ17268@jukie.net>
References: <87y6ly45fc.fsf@59A2.org> <20091122213649.GJ17268@jukie.net>
Date: Sun, 22 Nov 2009 22:43:30 +0100
Message-ID: <87ws1i44n1.fsf@59A2.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: notmuch@notmuchmail.org
Subject: Re: [notmuch] [RFC] Precedence of OR and AND
Precedence: list

On Sun, 22 Nov 2009 16:36:49 -0500, Bart Trojanowski <bart@jukie.net> wrote:
> Wouldn't this problem be solved by each filter appending a bracketed
> version of your filter?
> 
> You start with tag:inbox and you filter on "term1 or term2" you'd get:
> 
>         tag:inbox and (term1 or term2)

Absolutely, and I have this applied locally to notmuch.el, but I didn't
fix notmuch-search-filter-by-tag because that would really need to parse
the expression.  I'm just asking if anyone else thinks binding OR
tighter than AND would be desirable.

Jed