On Sat, Aug 27 2016, Erik Rybakken wrote:
> Hi,
>
> Thanks Tomi and David for the feedback!
>
> On Fri, Aug 26, 2016 at 02:32:19PM +0300, Tomi Ollila wrote:
>
>> ... but I can think of one problem there (if my memory server correctly)
>
> Yeah, I didn't think of that.
Yuri D'Elia writes:
>
> What's your POV on this? Is it expected/useful in some scenario?
>
> I'd expect all terms to follow the same rules for consistency.
For terms where each document (mail message) has only one term with a
given prefix, OR is a more natural default, since
On Mon, Aug 29 2016, David Bremner wrote:
> Yuri D'Elia writes:
>
>> term1 AND (tag:term2 OR tag:term3)
>>
>> am I right? Is this a feature of the xapian query syntax? (can it be
>> tweaked to _unconditionally_ AND all terms?)
>
> This is most likely a
Yuri D'Elia writes:
> term1 AND (tag:term2 OR tag:term3)
>
> am I right? Is this a feature of the xapian query syntax? (can it be
> tweaked to _unconditionally_ AND all terms?)
This is most likely a feature of the "grouping" parameter in
QueryParser::add_boolean_prefix. It
On Mon, Aug 29 2016, Charlie Allom wrote:
> You can debug what the real query is by adding NOTMUCH_DEBUG_QUERY=1 to
> your search:
>
> 12:29 YELP-CHARLIE~[local@2.7.12] % NOTMUCH_DEBUG_QUERY=1 notmuch search
> 'term1 (tag:term2 tag:term3)'
> Query string is:
>
You can debug what the real query is by adding NOTMUCH_DEBUG_QUERY=1 to
your search:
12:29 YELP-CHARLIE~[local@2.7.12] % NOTMUCH_DEBUG_QUERY=1 notmuch search
'term1 (tag:term2 tag:term3)'
Query string is:
term1 (tag:term2 tag:term3)
Exclude query is:
Xapian::Query((Kdeleted OR Kspam OR
Hi everyone,
I'm a bit baffled by the query syntax. Reading the manual:
``Each term in the query will be implicitly connected by a logical AND
if no explicit operator is provided (except that terms with a common
prefix will be implicitly combined with OR).''
I would have assumed that:
term1