search for: notmuch_debug_query

Displaying 3 results from an estimated 3 matches for "notmuch_debug_query".

2018 Sep 29
2
xapian parser bug?
Today we noticed that keywords can't be searched as prefixed terms. Or that's what it looks like anyway. I tested and, or, and not. ╰─% NOTMUCH_DEBUG_QUERY=y notmuch search 'subject:"and"' Query string is: subject:"and" notmuch search: A Xapian exception occurred A Xapian exception occurred parsing query: Syntax: <expression> AND <expression> Query string was: subject:"and" ╰─% NOTMUCH_DEBUG_QUERY=y n...
2018 Sep 30
0
xapian parser bug?
...happen in those situations any more). J > On 29 Sep 2018, at 23:09, David Bremner <david at tethera.net> wrote: > > > Today we noticed that keywords can't be searched as prefixed terms. Or > that's what it looks like anyway. I tested and, or, and not. > > ╰─% NOTMUCH_DEBUG_QUERY=y notmuch search 'subject:"and"' > Query string is: > subject:"and" > notmuch search: A Xapian exception occurred > A Xapian exception occurred parsing query: Syntax: <expression> AND <expression> > Query string was: subject:"and" &gt...
2017 Mar 09
3
Inconsistent query results
...nd where the bug is, but I think it's safe to say it's not in your code. I made a somewhat simpler test case that displays the same problem (at the end). I'm also fairly sure this is different than the exclude related bug I recently fixed in notmuch, since running your test under "NOTMUCH_DEBUG_QUERY=yes ./test" shows the same xapian query is used both times. One thing I noticed is that if run both your test case and mine under valgrind, I get a report of some uninitialized memory. The reports are similar in both cases, here is part of the report from my test case ==11180== Conditional j...