X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=manpages%2Fnotmuch-search-terms-7.mdwn;h=ccc203fabb444d2ddaf1cdb54faa31f4c95ca58d;hb=39aab76514c6f6f2b6769b9fd45fd9570664fa49;hp=e4058119ede883288b345efce4d6fd7698e93aa9;hpb=e4734d2e839d916a78d295c76eff880574c327db;p=notmuch-wiki

diff --git a/manpages/notmuch-search-terms-7.mdwn b/manpages/notmuch-search-terms-7.mdwn
index e405811..ccc203f 100644
--- a/manpages/notmuch-search-terms-7.mdwn
+++ b/manpages/notmuch-search-terms-7.mdwn
@@ -57,6 +57,10 @@
 
        · date:<since>..<until>
 
+       · lastmod:<initial-revision>..<final-revision>
+
+       · query:<name>
+
        The <b>from:</b> prefix is used to match the name or address of the sender  of
        an email message.
 
@@ -122,6 +126,16 @@
 
        Each  timestamp  is  a  number representing the number of seconds since
        1970-01-01 00:00:00 UTC.
+
+       The <b>lastmod:</b> prefix can be used to restrict the result by the  database
+       revision  number  of  when  messages  were  last  modified  (tags  were
+       added/removed or filenames changed).  This is usually used in  conjunc‐
+       tion  with  the <b>--uuid</b> argument to <b>notmuch</b> <b>search</b> to find messages that
+       have changed since an earlier query.
+
+       The <b>query:</b> prefix allows queries to refer to previously  saved  queries
+       added  with <a href='../notmuch-config-1/'>notmuch-config</a>(1). Named queries are only available if not‐
+       much is built with <b>Xapian</b> <b>Field</b> <b>Processors</b> (see below).
 </pre>
 
 <h3> &nbsp; Operators</h3>
@@ -189,14 +203,11 @@
        flexible <b>term</b> based searching. The prefixes currently supported by not‐
        much are as follows.
 
-              ┌───────────────────────────┬────────────────────────────┐
-              │Boolean
-              ├───────────────────────────┼────────────────────────────┤
-              │
-              │
-              │       <b>thread:</b>     <b>folder:</b> │        <b>subject:</b>    <b>attach‐</b> │
-              │       <b>path:</b>               │        <b>ment:</b> <b>mimetype:</b>     │
-              └───────────────────────────┴────────────────────────────┘
+       <b>Boolean</b>
+              <b>tag:</b>, <b>id:</b>, <b>thread:</b>, <b>folder:</b>, <b>path:</b>
+
+       <b>Probabilistic</b>
+              <b>from:</b>, <b>to:</b>, <b>subject:</b>, <b>attachment:</b>, <b>mimetype:</b>
 </pre>
 
 <h3> &nbsp; Terms and phrases</h3>
@@ -254,7 +265,14 @@
        could describe (the end of yesterday). Similarly,  date:january..febru‐
        ary matches from the beginning of January to the end of February.
 
-       Currently,  we  do  not  support  spaces  in range expressions. You can
+       date:&lt;expr&gt;..!  can be used as a shorthand for date:&lt;expr&gt;..&lt;expr&gt;. The
+       expansion takes place before interpretation,  and  thus,  for  example,
+       date:monday..!  matches  from  the beginning of Monday until the end of
+       Monday.  With <b>Xapian</b> <b>Field</b> <b>Processor</b>  support  (see  below),  non-range
+       date  queries such as date:yesterday will work, but otherwise will give
+       unexpected results; if in doubt use date:yesterday..!
+
+       Currently, we do not support  spaces  in  range  expressions.  You  can
        replace the spaces with &apos;_&apos;, or (in most cases) &apos;-&apos;, or (in some cases)
        leave  the  spaces out altogether. Examples in this man page use spaces
        for clarity.
@@ -263,11 +281,6 @@
        ble  to specify date:..&lt;until&gt; or date:&lt;since&gt;.. to not limit the start
        or end time, respectively. Pre-1.2.1 Xapian does not report an error on
        open ended ranges, but it does not work as expected either.
-
-       Entering  date:expr  without  &quot;..&quot;  (for  example date:yesterday) won&apos;t
-       work, as it&apos;s not interpreted as a range expression  at  all.  You  can
-       achieve  the expected result by duplicating the expr both sides of &quot;..&quot;
-       (for example date:yesterday..yesterday).
 </pre>
 
 <h3> &nbsp; Relative date and time</h3>
@@ -344,6 +357,22 @@
        Some time zone codes, e.g. UTC, EET.
 </pre>
 
+<h2>XAPIAN FIELD PROCESSORS</h2>
+<pre>
+       Certain optional features of the notmuch query processor  rely  on  the
+       presence  of  the Xapian field processor API. You can determine if your
+       notmuch was built against a sufficiently recent version  of  Xapian  by
+       running
+
+          % notmuch config get built_with.field_processor
+
+       Currently the following features require field processor support:
+
+       · non-range date queries, e.g. &quot;date:today&quot;
+
+       · named queries e.g. &quot;query:my_special_query&quot;
+</pre>
+
 <h2>SEE ALSO</h2>
 <pre>
        <a href='../notmuch-1/'>notmuch</a>(1), <a href='../notmuch-config-1/'>notmuch-config</a>(1), <a href='../notmuch-count-1/'>notmuch-count</a>(1), <a href='../notmuch-dump-1/'>notmuch-dump</a>(1),  <a href='../notmuch-hooks-5/'>not‐</a>
@@ -358,7 +387,7 @@
 
 <h2>COPYRIGHT</h2>
 <pre>
-       2014, Carl Worth and many others
+       2009-2016, Carl Worth and many others
 </pre>
 
-<h2>0.20.1</h2>
+<h2>0.22</h2>