unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jameson Rollins <jrollins@finestructure.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: bug report: xapian error for message id with '..'
Date: Wed, 28 Apr 2010 18:41:18 -0400	[thread overview]
Message-ID: <87vdbbw67l.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87y6g7zr6q.fsf@servo.finestructure.net>

[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]

I have a followup on this report.  Olly suggested quoting the quoting of
the id, so that the quoting gets properly passed to Xapian, and that
seems to work:

0 servo:~ $ notmuch search id:'"4bd73e8cb3d79_1a3c..fb637ff610e@skinner.tmail"'
thread:000000000000c4cf  Yest. 15:44 [1/1] XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
0 servo:~ $ 

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.

On Wed, 28 Apr 2010 08:39:57 -0400, Jameson Rollins <jrollins@finestructure.net> wrote:
> 0 servo$ notmuch search id:4bd73e8cb3d79_1a3c..fb637ff610e@skinner.tmail
> A Xapian exception occurred performing query: Unknown range operation
> Query string was: id:4bd73e8cb3d79_1a3c..fb637ff610e@skinner.tmail
> 0 servo$ 

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.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2010-04-28 22:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28 12:39 bug report: xapian error for message id with '..' Jameson Rollins
2010-04-28 22:41 ` Jameson Rollins [this message]
2010-10-23  0:48   ` Carl Worth
2010-10-23  1:05     ` Carl Worth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vdbbw67l.fsf@servo.finestructure.net \
    --to=jrollins@finestructure.net \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).