* Re: Bug#755246: notmuch-mutt: search that returns whole threads
[not found] ` <20140722114049.GB30408@upsilon.cc>
@ 2014-07-25 10:08 ` David Bremner
0 siblings, 0 replies; only message in thread
From: David Bremner @ 2014-07-25 10:08 UTC (permalink / raw)
To: Stefano Zacchiroli, 755246; +Cc: Vagrant Cascadian, Notmuch Mail
Stefano Zacchiroli <zack@debian.org> writes:
>
> In fact, I was hoping in some sort of meta-syntax, to piggyback on. For
> instance, if "field:value" is something that is always threated
> specially by notmuch, we can use something like "notmuch:threads" (vs,
> say, "notmuch:nothreads") and strip it before it hits notmuch.
>
> If you've no objection to this, I can implement something like it.
(bringing in the upstream list, as this is really an upstream design
issue)
Currently any unrecognized field:value will be searched for as a phrase
[1], and is equivalent to "field value", field.value, field-value, among
others. So as long as notmuch: is not a recognized prefix, your scheme
will not block any searches.
It doesn't seem especially likely that we'll want to use "notmuch:" as a
prefix; of course if you were to choose something with "mutt" in the
name that would be more nearly a sure thing.
[1]: http://xapian.org/docs/queryparser.html
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-07-25 10:08 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20140719025928.GA25672@siren>
[not found] ` <20140719173500.GA9660@upsilon.cc>
[not found] ` <20140719210111.GA28049@siren>
[not found] ` <20140719211106.GA26819@upsilon.cc>
[not found] ` <874my9elz7.fsf@maritornes.cs.unb.ca>
[not found] ` <20140722114049.GB30408@upsilon.cc>
2014-07-25 10:08 ` Bug#755246: notmuch-mutt: search that returns whole threads David Bremner
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).