From: Gaute Hope <eg@gaute.vetsj.com>
To: David Bremner <david@tethera.net>, Jani Nikula <jani@nikula.org>,
notmuch@notmuchmail.org
Subject: Re: [PATCH] WIP: add thread subqueries.
Date: Thu, 07 Sep 2017 17:47:34 +0000 [thread overview]
Message-ID: <1504806079.rug5z5bxr4.astroid@strange.none> (raw)
In-Reply-To: <87efs5g0sq.fsf@tethera.net>
David Bremner writes on august 21, 2017 3:35:
> David Bremner <david@tethera.net> writes:
>
>
>> If you're interested in this feature, please test, let me know if it's
>> workable for your use case. The syntax here is thread:{$query}. The
>> usual caveats about whitespace apply. The running example is
>>
>> thread:{from:me} and thread:{from:jian} and not thread:{from:dave}
>>
>
> I was playing around with this, and
>
> 'thread:"{from:bremner and date:2017}"' and thread:{from:sitaram}
>
> is about 10x faster than without the date restriction. This is roughly
> proportional to the number of threads matching the first subquery.
> Unfortunately the date restriction needs to be inside the subquery with
> the current design.
So just to clarify; to make true full thread searches there cannot be more than one term in each thread:{} query? Otherwise, all terms in each thread: query must be found in at least one message at the same time. So you could put the date: restriction in a separate thread:{}, but it would be slower?
-gaute
next prev parent reply other threads:[~2017-09-07 17:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 21:55 find threads where I and Jian participated but not Dave Xu Wang
2017-06-13 15:57 ` Xu Wang
2017-06-13 23:31 ` David Bremner
2017-06-14 0:24 ` Xu Wang
2017-06-14 3:32 ` Brian Sniffen
2017-06-15 17:54 ` Daniel Kahn Gillmor
2017-06-15 20:20 ` David Bremner
2017-06-16 1:07 ` Matt Armstrong
2017-06-16 6:28 ` Gaute Hope
2017-06-21 20:04 ` Matt Armstrong
2017-06-21 21:30 ` Daniel Kahn Gillmor
2017-06-22 6:08 ` Gaute Hope
2017-06-22 6:22 ` Gaute Hope
2017-06-23 0:00 ` Matt Armstrong
2017-06-25 15:46 ` finding incoming messages in threads in which i've participated [was: Re: find threads where I and Jian participated but not Dave] Daniel Kahn Gillmor
2017-06-25 17:14 ` David Bremner
2017-06-26 20:49 ` Matt Armstrong
2017-06-26 23:09 ` David Bremner
2017-08-20 13:35 ` Jani Nikula
2017-08-20 13:48 ` Jani Nikula
2017-08-20 21:32 ` [PATCH] WIP: add thread subqueries David Bremner
2017-08-21 1:35 ` David Bremner
2017-09-07 17:47 ` Gaute Hope [this message]
2017-09-07 18:51 ` David Bremner
2017-06-25 17:40 ` finding incoming messages in threads in which i've participated [was: Re: find threads where I and Jian participated but not Dave] Brian Sniffen
2017-06-26 20:54 ` Matt Armstrong
2017-06-22 20:15 ` find threads where I and Jian participated but not Dave Matt Armstrong
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=1504806079.rug5z5bxr4.astroid@strange.none \
--to=eg@gaute.vetsj.com \
--cc=david@tethera.net \
--cc=jani@nikula.org \
--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).