search for: and_not

...Something about turning on phrase parsing maybe? ╰─% NOTMUCH_DEBUG_QUERY=y notmuch count 'subject:" not "' Query string is: subject:" not " Exclude query is: Query((((Kspam OR Kdeleted) OR Kmuted) OR Kbad-address)) Final query is: Query(((Tmail AND 0 * XSUBJECTnot at 1) AND_NOT (((Kspam OR Kdeleted) OR Kmuted) OR Kbad-address))) 9927

Hi, I want to print all the records from the passed database when the search string is not present. I quickly skimmed through the API but I couldn't find a way to do it. Can someone show some pointers. Thanks, Shri

..., and from your output I believe you're not > (the * in the query description I believe doesn't happen in those > situations any more). 1.4.4 and later eliminate redundant 0 scaling factors, but this one isn't actually redundant: > > Query(((Tmail AND 0 * XSUBJECTnot at 1) AND_NOT (((Kspam OR Kdeleted) OR Kmuted) OR Kbad-address))) If it was on the right-hand side of AND_NOT it would be eliminated (because the right-hand side doesn't contribute any weight anyway). FWIW, I also couldn't reproduce this (I tried with quest and 1.4.7): $ quest -psubject:S -fdefault,bo...

I've now uploaded Xapian 1.0.1, which you can download from the usual place: http://www.xapian.org/download.php This release mainly comprises bug fixes and performance improvements. The "simple" examples (for both C++ and the bindings) have also been overhauled and now use the QueryParser and TermGenerator classes, which makes for simpler examples and should better reflect

I've now uploaded Xapian 1.0.1, which you can download from the usual place: http://www.xapian.org/download.php This release mainly comprises bug fixes and performance improvements. The "simple" examples (for both C++ and the bindings) have also been overhauled and now use the QueryParser and TermGenerator classes, which makes for simpler examples and should better reflect

"Kirill A. Shutemov" <kirill at shutemov.name> writes: > Hello, > > I found that on particular queries notmuch return different results if run > the query few times. Re-initialing the query or db doesn't help. > > I've attached test case along with corpus of messages. > > Unpack the archive and run `make' there. It will initialize the notmuch

...e problem (at the end). It's a bug in Xapian - I've committed a fix to master (commit fa12a83957e97349aa6e2a6c0896faf210dfe4b4) which I'll backport for 1.4.4 and 1.2.25 (it also affects 1.2.x). To trigger it you need an AND operator which is unweighted (e.g. being on the right side of AND_NOT here) with a subquery which uses the passed max weight value (the obvious case is another operator, OR in this case). (David already confirmed on IRC that the fix applied solves this for him.) Cheers, Olly

...g maybe? > > ╰─% NOTMUCH_DEBUG_QUERY=y notmuch count 'subject:" not "' > Query string is: > subject:" not " > Exclude query is: > Query((((Kspam OR Kdeleted) OR Kmuted) OR Kbad-address)) > Final query is: > Query(((Tmail AND 0 * XSUBJECTnot at 1) AND_NOT (((Kspam OR Kdeleted) OR Kmuted) OR Kbad-address))) > 9927 > -- James Aylett devfort.com — spacelog.org — tartarus.org/james/

In current Xapian SVN HEAD, there is a bug in the query parser concerned with the handling of wildcard terms with a "+" prefix. Specifically, a query such as "+foo* bar" will be parsed by the query parser into Xapian::Query("bar") if there are no terms in the database which start "foo". Instead, since the "+" term cannot be matched, I believe