Re: Do path: searches handle spaces correctly?

diff --git a/9b/e98e3121296919935eb4052f9747697534cc1f b/9b/e98e3121296919935eb4052f9747697534cc1f
new file mode 100644 (file)
index 0000000..1e78121
--- /dev/null
+++ b/9b/e98e3121296919935eb4052f9747697534cc1f
@@ -0,0 +1,84 @@
+Return-Path: <camalot@picnicpark.org>\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 26F86431FAF\r
+       for <notmuch@notmuchmail.org>; Mon, 22 Sep 2014 22:27:35 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       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 MzmTKJXbsZ7D for <notmuch@notmuchmail.org>;\r
+       Mon, 22 Sep 2014 22:27:30 -0700 (PDT)\r
+Received: from picnicpark.org (picnicpark.org [130.94.181.238])\r
+       by olra.theworths.org (Postfix) with ESMTP id 873C3431FAE\r
+       for <notmuch@notmuchmail.org>; Mon, 22 Sep 2014 22:27:30 -0700 (PDT)\r
+Received: (qmail 53178 invoked by uid 13806); 23 Sep 2014 05:27:29 -0000\r
+Received: from unknown (HELO gw.picnicpark.org) ([108.225.17.54])\r
+       (envelope-sender <camalot@picnicpark.org>)\r
+       by 130.94.181.238 (qmail-ldap-1.03) with SMTP\r
+       for <aclements@csail.mit.edu>; 23 Sep 2014 05:27:29 -0000\r
+Received: from friend.picnicpark.org (friend.picnicpark.org [192.168.35.1])\r
+       by gw.picnicpark.org (Postfix) with ESMTPSA id 8D71112A0D9D;\r
+       Mon, 22 Sep 2014 22:27:29 -0700 (PDT)\r
+Message-ID: <1411450049.1931.93.camel@picnicpark.org>\r
+Subject: Re: Do path: searches handle spaces correctly?\r
+From: Keith Amidon <camalot@picnicpark.org>\r
+To: Austin Clements <aclements@csail.mit.edu>\r
+Date: Mon, 22 Sep 2014 22:27:29 -0700\r
+In-Reply-To: <20140922150607.GA7970@csail.mit.edu>\r
+References: <878uleklvt.fsf@awakenetworks.com>\r
+       <87tx40ggf1.fsf@maritornes.cs.unb.ca>\r
+       <1411396931.1931.91.camel@picnicpark.org>\r
+       <20140922150607.GA7970@csail.mit.edu>\r
+Content-Type: text/plain; charset="UTF-8"\r
+X-Mailer: Evolution 3.12.5 \r
+Mime-Version: 1.0\r
+Content-Transfer-Encoding: 7bit\r
+Cc: 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: Tue, 23 Sep 2014 05:27:35 -0000\r
+\r
+On Mon, 2014-09-22 at 15:06 +0000, Austin Clements wrote:\r
+> I assume you're doing this from the command line?  Does the following\r
+> work?\r
+> \r
+> notmuch search --output=files 'path:"dir/INBOX/INBOX/Sent Items/**"'\r
+> \r
+> Shell quoting and Xapian quoting interact in often confusing ways.  In\r
+> your original command line, the single quotes suppress shell argument\r
+> splitting, but never make it to notmuch, so notmuch sees two search\r
+> terms "path:dir/INBOX/INBOX/Sent" and "Items/**".  In the command line\r
+> I suggested, the single quotes play the same role, but for the entire\r
+> query.  Because of the quoting, notmuch *does* see the inner double\r
+> quotes, which makes the path a single term (note that Xapian only\r
+> accepts double quotes, not single quotes).  In general, it's good to\r
+> enclose the entire command line query in single quotes so shell\r
+> parsing doesn't get in the way of query parsing.\r
+\r
+Bingo.  That was it.  Thanks for clarifying how the quoting interacts. \r
+\r
+What do you think about adding a section to the notmuch-search-terms web\r
+page that talks in more detail about the quoting interactions?  If there\r
+were on obvious section about this in the man page it might have helped\r
+me find the issue myself.  If this seems like a good idea I'll take a\r
+crack at it later this week when I get time to research the Xapian\r
+quoting in a bit more detail.\r
+\r
+        --- Keith\r
+\r