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