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 1E395431FD0 for ; Wed, 2 Feb 2011 14:53:19 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.99 X-Spam-Level: X-Spam-Status: No, score=-0.99 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, T_MIME_NO_TEXT=0.01] autolearn=disabled 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 H6bEj7W57CNV; Wed, 2 Feb 2011 14:53:18 -0800 (PST) Received: from yoom.home.cworth.org (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 7548C431FB5; Wed, 2 Feb 2011 14:53:18 -0800 (PST) Received: by yoom.home.cworth.org (Postfix, from userid 1000) id DD48E2540DE; Thu, 3 Feb 2011 08:48:50 +1000 (EST) From: Carl Worth To: Austin Clements , notmuch@notmuchmail.org Subject: Re: [RFC PATCH v2 0/8] Custom query parser, date search, folder search, and more In-Reply-To: <20110202050336.GB28537@mit.edu> References: <1295165458-9573-1-git-send-email-amdragon@mit.edu> <20110202050336.GB28537@mit.edu> User-Agent: Notmuch/0.5 (http://notmuchmail.org) Emacs/23.2.1 (i486-pc-linux-gnu) Date: Wed, 02 Feb 2011 14:48:50 -0800 Message-ID: <87sjw6hx2l.fsf@yoom.home.cworth.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 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: Wed, 02 Feb 2011 22:53:19 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable Restricting my reply to one tiny bit of your mail: You wrote: > non-recursive is the only thing that makes sense for Maildir++ folders Either I'm not understanding Maildir++ folders, or I don't agree with you. I might have an email archive that looks like this: Maildir .work .project1 .project2 .etc... .family .dad .mom .brother .etc... With the above setup, what would be unreasonable about wanting to search for all work-related messages (across all projects, say) with a string like "folder:work" ? Now, a person might definitely want to search for messages in the ".work" folder directly, (not including the sub-folders), so we should provide support for users to get at that behavior as well, (such as a proposed "folder:work$" or so). To me, both cases are perfectly legitimate, and I don't understand an argument that claims that only one makes sense. (Or again, I may be misunderstanding something.) =2DCarl =2D-=20 carl.d.worth@intel.com --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFNSd9S6JDdNq8qSWgRAhnIAJ9h/FR1ZT4D+HnzrsqXc+cCK0zYNACeKX2D DG/7w04XQ5gmIFbyHRMMdyI= =cX3r -----END PGP SIGNATURE----- --=-=-=--