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.
On Wed, 28 Apr 2010 18:41:18 -0400, Jameson Rollins
jroll...@finestructure.net 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
On Fri, 22 Oct 2010 17:48:29 -0700, Carl Worth cwo...@cworth.org wrote:
On Wed, 28 Apr 2010 18:41:18 -0400, Jameson Rollins
jroll...@finestructure.net wrote:
I also note here that notmuch is not returning an error, even though a
Xapian exception occurred and the search failed. This is
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 at
skinner.tmail"'
thread:c4cf Yest. 15:44 [1/1]
I have received a message with a somewhat strange message Id that is
causing problems in notmuch:
Message-Id: <4bd73e8cb3d79_1a3c..fb637ff610e at skinner.tmail>
Notmuch (or actually Xapian) seems to be interpreting the '..' as a
range operator, which it doesn't know how to handle:
0 servo$
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..fb637ff6...@skinner.tmail'
thread:c4cf Yest. 15:44 [1/1]
