Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id BED64431FBC for ; Sun, 22 Nov 2009 13:47:46 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qWxUa7ZDkW9l for ; Sun, 22 Nov 2009 13:47:46 -0800 (PST) Received: from tau.jukie.net (tau.jukie.net [216.239.93.128]) by olra.theworths.org (Postfix) with ESMTP id 08147431FAE for ; Sun, 22 Nov 2009 13:47:46 -0800 (PST) Received: by tau.jukie.net (Postfix, from userid 1000) id 8B990C02F86; Sun, 22 Nov 2009 16:47:45 -0500 (EST) Date: Sun, 22 Nov 2009 16:47:45 -0500 From: Bart Trojanowski To: Jed Brown Message-ID: <20091122214745.GK17268@jukie.net> References: <87y6ly45fc.fsf@59A2.org> <20091122213649.GJ17268@jukie.net> <87ws1i44n1.fsf@59A2.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87ws1i44n1.fsf@59A2.org> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: notmuch@notmuchmail.org Subject: Re: [notmuch] [RFC] Precedence of OR and AND X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Nov 2009 21:47:46 -0000 * Jed Brown [091122 16:43]: > 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. Maybe some of the ambiguity would go away if we used && and || instead of AND and OR. Then no matter the default, we could distinguish if someone meant 2 or 3 tags when they typed in 'foo and bar'. -Bart -- WebSig: http://www.jukie.net/~bart/sig/