From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Mark Walters <markwalters1009@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [WIP 0/2] Thread based searching
Date: Sat, 14 Apr 2012 12:15:09 -0700 [thread overview]
Message-ID: <87y5pyyvk2.fsf@servo.finestructure.net> (raw)
In-Reply-To: <1332274320-17487-1-git-send-email-markwalters1009@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
On Tue, Mar 20 2012, Mark Walters <markwalters1009@gmail.com> wrote:
> It implements a very crude form of thread based search: the user can
> ask for all the threads that have a message matching the primary query
> and have a (possibly different) message matching a secondary query.
>
> For example notmuch search --secondary-search from:A :AND: from:B
> returns all threads that have a message from A and a message from B.
Hey, Mark. I think this is a useful idea, but I think the
implementation is more complicated than it needs to be. I would rather
just have a switch that allows me to search by thread, instead of by
message. Something like just --by-thread would work for me.
I guess it might be nice to have such fined grain control to specify
independent search terms for both messages and threads simultaneously,
but I really don't think I would ever use such capabilities, and the
additional syntax is a little confusing. But I certainly would use the
ability to search entire threads instead of just messages.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
prev parent reply other threads:[~2012-04-14 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 20:11 [WIP 0/2] Thread based searching Mark Walters
2012-03-20 20:11 ` [WIP 1/2] lib: multithread Mark Walters
2012-03-20 20:12 ` [WIP 2/2] cli: search: multithread Mark Walters
2012-04-14 19:15 ` Jameson Graef Rollins [this message]
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=87y5pyyvk2.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=markwalters1009@gmail.com \
--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).