Re: Inspired but need help searching folder names containing spaces

diff --git a/cc/6737a67c1d9909f77df92dd02e70f0420dee1e b/cc/6737a67c1d9909f77df92dd02e70f0420dee1e
new file mode 100644 (file)
index 0000000..2feffc9
--- /dev/null
+++ b/cc/6737a67c1d9909f77df92dd02e70f0420dee1e
@@ -0,0 +1,77 @@
+Return-Path: <david@tethera.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 9F7B3431FC7\r
+       for <notmuch@notmuchmail.org>; Sat, 28 Feb 2015 01:13:57 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 2.438\r
+X-Spam-Level: **\r
+X-Spam-Status: No, score=2.438 tagged_above=-999 required=5\r
+       tests=[DNS_FROM_AHBL_RHSBL=2.438] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id 220HswICT1ha for <notmuch@notmuchmail.org>;\r
+       Sat, 28 Feb 2015 01:13:54 -0800 (PST)\r
+Received: from mx.xen14.node3324.gplhost.com (gitolite.debian.net\r
+       [87.98.215.224])\r
+       (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 5B2D7431FB6\r
+       for <notmuch@notmuchmail.org>; Sat, 28 Feb 2015 01:13:54 -0800 (PST)\r
+Received: from remotemail by mx.xen14.node3324.gplhost.com with local (Exim\r
+       4.80) (envelope-from <david@tethera.net>)\r
+       id 1YRdMl-0004a8-GB; Sat, 28 Feb 2015 09:07:19 +0000\r
+Received: (nullmailer pid 25864 invoked by uid 1000); Sat, 28 Feb 2015\r
+       09:07:06 -0000\r
+From: David Bremner <david@tethera.net>\r
+To: Matthew Lear <matt@bubblegen.co.uk>, Jani Nikula <jani@nikula.org>\r
+Subject: Re: Inspired but need help searching folder names containing spaces\r
+In-Reply-To: <79D823A8-925A-478E-9734-9702C311A4F8@bubblegen.co.uk>\r
+References: <54E3BAE1.1030004@bubblegen.co.uk>\r
+       <87pp97sldj.fsf@maritornes.cs.unb.ca>\r
+       <ed7f5ff35a6d784885b68666fe5b5898.squirrel@webmail.plus.net>\r
+       <87zj88wjgy.fsf@nikula.org>\r
+       <79D823A8-925A-478E-9734-9702C311A4F8@bubblegen.co.uk>\r
+User-Agent: Notmuch/0.19+48~gb74ed1c (http://notmuchmail.org) Emacs/24.4.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Sat, 28 Feb 2015 10:07:06 +0100\r
+Message-ID: <87wq328kw5.fsf@maritornes.cs.unb.ca>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sat, 28 Feb 2015 09:13:57 -0000\r
+\r
+Matthew Lear <matt@bubblegen.co.uk> writes:\r
+\r
+>\r
+> Thanks. Explains everything. Any thoughts on searching on 'to' only?\r
+> I'm not sure if this is also related to what Xapian needs to be\r
+> provided with. If not, and if only searching in the to, cc and bcc\r
+> fields of the header is possible, maybe we could consider adopting and\r
+> integrating case sensitive syntax in notmuch such as TO:me rather than\r
+> to:me..?\r
+\r
+I'm not sure about the exact syntax, but some separate prefix to mean\r
+only in the To header would be possible. As far as I know we'd need to\r
+add more terms to the database [1], so you'd need to convince people\r
+that the increase in the size of everyone's database was worthwhile. And\r
+of course someone needs to write the code, but it would not be that\r
+hard, I think. \r
+\r
+d\r
+\r
+[1]: this could also be solved with the semi-mythical custom query parser.\r