Re: bug report: xapian error for message id with '..'

diff --git a/de/9efbdaaacff04764ddf0dd4bc0d2fb8bcb15c8 b/de/9efbdaaacff04764ddf0dd4bc0d2fb8bcb15c8
new file mode 100644 (file)
index 0000000..65c3caa
--- /dev/null
+++ b/de/9efbdaaacff04764ddf0dd4bc0d2fb8bcb15c8
@@ -0,0 +1,105 @@
+Return-Path: <cworth@cworth.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 82CB340D151\r
+       for <notmuch@notmuchmail.org>; Fri, 22 Oct 2010 17:48:46 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.89\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.89 tagged_above=-999 required=5\r
+       tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, T_MIME_NO_TEXT=0.01]\r
+       autolearn=ham\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 Ums0+3wg6NpZ; Fri, 22 Oct 2010 17:48:35 -0700 (PDT)\r
+Received: from yoom.home.cworth.org (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 80FCB40D148;\r
+       Fri, 22 Oct 2010 17:48:35 -0700 (PDT)\r
+Received: by yoom.home.cworth.org (Postfix, from userid 1000)\r
+       id 22BAA254493; Fri, 22 Oct 2010 17:48:35 -0700 (PDT)\r
+From: Carl Worth <cworth@cworth.org>\r
+To: Jameson Rollins <jrollins@finestructure.net>,\r
+       Notmuch Mail <notmuch@notmuchmail.org>\r
+Subject: Re: bug report: xapian error for message id with '..'\r
+In-Reply-To: <87vdbbw67l.fsf@servo.finestructure.net>\r
+References: <87y6g7zr6q.fsf@servo.finestructure.net>\r
+       <87vdbbw67l.fsf@servo.finestructure.net>\r
+User-Agent: Notmuch/0.3.1-90-g8071c5c (http://notmuchmail.org) Emacs/23.2.1\r
+       (i486-pc-linux-gnu)\r
+Date: Fri, 22 Oct 2010 17:48:29 -0700\r
+Message-ID: <87pqv1u42q.fsf@yoom.home.cworth.org>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+       micalg=pgp-sha1; protocol="application/pgp-signature"\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, 23 Oct 2010 00:48:46 -0000\r
+\r
+--=-=-=\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On Wed, 28 Apr 2010 18:41:18 -0400, Jameson Rollins <jrollins@finestructure=\r
+.net> wrote:\r
+> So I think this means that the problem probably lies mostly in the emacs\r
+> UI not properly quoting the id string.  What originally got me on this\r
+> problem is that I was not able to manipulate the tag of this email from\r
+> within emacs.\r
+\r
+Hi Jameson,\r
+\r
+Thanks for reporting that problem. (And thanks for mentioning that the\r
+problem occurred when trying to manipulate tags---I was having trouble\r
+finding the operation that wouldn't work with the problematic ID.)\r
+\r
+I've just added a test case to our test suite to cover this. Then I also\r
+added a fix to the emacs code to properly quote message IDs to resolve\r
+the problem.\r
+\r
+There might still be other quoting problems here or there in the emacs\r
+interface, so let me know if you find anything else. But at least a\r
+large class of problems is fixed here.\r
+\r
+> I also note here that notmuch is not returning an error, even though a\r
+> Xapian exception occurred and the search failed.  This is another\r
+> important issue.  I'm not sure if I should bring it up in a separate\r
+> message or not.  This goes back to the bug tracking issue.\r
+\r
+A separate message would be preferred for me. I'm basically using tagged\r
+messages to indicate open bugs, so I'm now stuck with being unable to\r
+untag this thread until both of these issues are fixed. And that's not\r
+ideal.\r
+\r
+=2DCarl\r
+\r
+PS. What's also obviously not ideal is that there's no external\r
+visibility of my "open bug queue". I'd definitely like to be able to\r
+easily advertise things like "No, I haven't forgotten about that bug you\r
+reported in April---I just haven't fixed it yet." Anyone want to write a\r
+nice "notmuch search --format=3Dhtml" for me?\r
+\r
+=2D-=20\r
+carl.d.worth@intel.com\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.10 (GNU/Linux)\r
+\r
+iD8DBQFMwjDd6JDdNq8qSWgRAmUuAJ0Y5nOEVPDch8T9NBMFZ2dX7q444wCcCsaj\r
+sApFqEwCEZQQU2QJmE3Ie9U=\r
+=M9Ia\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r