manpages updates for release 0.32

[notmuch-wiki] / manpages / notmuch-search-terms-7.mdwn

diff --git a/manpages/notmuch-search-terms-7.mdwn b/manpages/notmuch-search-terms-7.mdwn
index d6d3241965f5a8d391025863190beb6c3d0e50f7..a2e11ef46c04ed04a82778fe29f1022f6303ca57 100644 (file)
--- a/manpages/notmuch-search-terms-7.mdwn
+++ b/manpages/notmuch-search-terms-7.mdwn
@@ -30,8 +30,8 @@
        terms/phrases in the body, the subject, or any of the sender or recipi‐
        ent headers.
 
        terms/phrases in the body, the subject, or any of the sender or recipi‐
        ent headers.
 

-       As  a  special  case,  a  search  string consisting of exactly a single
-       asterisk ("*") will match all messages.
+       As  a  special case, a search string consisting of exactly a single as‐
+       terisk ("*") will match all messages.

 </pre>
 
 <h3> &nbsp; Search prefixes</h3>
 </pre>
 
 <h3> &nbsp; Search prefixes</h3>


@@ -107,8 +107,8 @@
               specified  relative  to  the  top-level maildir (and without the
               leading slash). By default, <b>path:</b> matches messages in the speci‐
               fied  directory only. The &quot;/**&quot; suffix can be used to match mes‐
               specified  relative  to  the  top-level maildir (and without the
               leading slash). By default, <b>path:</b> matches messages in the speci‐
               fied  directory only. The &quot;/**&quot; suffix can be used to match mes‐

-              sages in the specified  directory  and  all  its  subdirectories
-              recursively.  <b>path:&quot;&quot;</b>  matches  messages in the root of the mail
+              sages in the specified directory and all its subdirectories  re‐
+              cursively.  <b>path:&quot;&quot;</b>  matches  messages  in  the root of the mail

               store and, likewise, <b>path:**</b> matches all messages.
 
               <b>path:</b> will find a message if <u>any</u> copy of that message is in  the
               store and, likewise, <b>path:**</b> matches all messages.
 
               <b>path:</b> will find a message if <u>any</u> copy of that message is in  the


@@ -120,8 +120,8 @@
               maildir, this includes messages in the &quot;new&quot; and &quot;cur&quot; subdirec‐
               tories. The exact syntax for maildir  folders  depends  on  your
               mail  configuration.  For maildir++, <b>folder:&quot;&quot;</b> matches the inbox
               maildir, this includes messages in the &quot;new&quot; and &quot;cur&quot; subdirec‐
               tories. The exact syntax for maildir  folders  depends  on  your
               mail  configuration.  For maildir++, <b>folder:&quot;&quot;</b> matches the inbox

-              folder (which is the root  in  maildir++),  other  folder  names
-              always start with &quot;.&quot;, and nested folders are separated by &quot;.&quot;s,
+              folder (which is the root in maildir++), other folder names  al‐
+              ways  start  with &quot;.&quot;, and nested folders are separated by &quot;.&quot;s,

               such as <b>folder:.classes.topology</b>. For &quot;file system&quot; maildir, the
               inbox is typically <b>folder:INBOX</b> and nested folders are separated
               by slashes, such as <b>folder:classes/topology</b>.
               such as <b>folder:.classes.topology</b>. For &quot;file system&quot; maildir, the
               inbox is typically <b>folder:INBOX</b> and nested folders are separated
               by slashes, such as <b>folder:classes/topology</b>.


@@ -165,8 +165,8 @@
               key can be present on a given  message  with  several  different
               values.  See <a href='../notmuch-properties-7/'>notmuch-properties</a>(7) for more details.
 
               key can be present on a given  message  with  several  different
               values.  See <a href='../notmuch-properties-7/'>notmuch-properties</a>(7) for more details.
 

-       User  defined  prefixes  are  also supported, see <a href='../notmuch-config-1/'>notmuch-config</a>(1) for
-       details.
+       User defined prefixes are also supported, see <a href='../notmuch-config-1/'>notmuch-config</a>(1) for de‐
+       tails.

 </pre>
 
 <h3> &nbsp; Operators</h3>
 </pre>
 
 <h3> &nbsp; Operators</h3>


@@ -216,8 +216,8 @@
 
        There are two ways to turn this off: a search for  a  capitalized  word
        will  be performed unstemmed, so that one can search for &quot;John&quot; and not
 
        There are two ways to turn this off: a search for  a  capitalized  word
        will  be performed unstemmed, so that one can search for &quot;John&quot; and not

-       get results for &quot;Johnson&quot;; phrase  searches  are  also  unstemmed  (see
-       below  for details).  Stemming is currently only supported for English.
+       get results for &quot;Johnson&quot;; phrase searches are also unstemmed (see  be‐
+       low  for  details).   Stemming is currently only supported for English.

        Searches for words in other languages will be performed unstemmed.
 </pre>
 
        Searches for words in other languages will be performed unstemmed.
 </pre>
 


@@ -229,10 +229,10 @@
 
 <h3> &nbsp; Boolean and Probabilistic Prefixes</h3>
 <pre>
 
 <h3> &nbsp; Boolean and Probabilistic Prefixes</h3>
 <pre>

-       Xapian  (and  hence  notmuch)  prefixes  are either <b>boolean</b>, supporting
-       exact matches like &quot;<u>tag:inbox</u>&quot;  or  <b>probabilistic</b>,  supporting  a  more
-       flexible  <b>term</b>  based searching. Certain <b>special</b> prefixes are processed
-       by notmuch in a way not strictly fitting either of  Xapian&apos;s  built  in
+       Xapian  (and hence notmuch) prefixes are either <b>boolean</b>, supporting ex‐
+       act matches like &quot;<u>tag:inbox</u>&quot; or <b>probabilistic</b>, supporting a more flexi‐
+       ble  <b>term</b>  based  searching.  Certain <b>special</b> prefixes are processed by
+       notmuch in a way not strictly  fitting  either  of  Xapian&apos;s  built  in

        styles. The prefixes currently supported by notmuch are as follows.
 
        <b>Boolean</b>
        styles. The prefixes currently supported by notmuch are as follows.
 
        <b>Boolean</b>


@@ -253,13 +253,13 @@
        occur in that order. One useful, but initially  surprising  feature  is
        that the following are equivalent ways to write the same phrase.
 
        occur in that order. One useful, but initially  surprising  feature  is
        that the following are equivalent ways to write the same phrase.
 

-       · &quot;a list of words&quot;
+       • &quot;a list of words&quot;

 
 

-       · a-list-of-words
+       • a-list-of-words

 
 

-       · a/list/of/words
+       • a/list/of/words

 
 

-       · a.list.of.words
+       • a.list.of.words

 
        Both parenthesised lists of terms and quoted phrases are ok with proba‐
        bilistic prefixes such as <b>to:</b>, <b>from:</b>, and <b>subject:</b>. In particular
 
        Both parenthesised lists of terms and quoted phrases are ok with proba‐
        bilistic prefixes such as <b>to:</b>, <b>from:</b>, and <b>subject:</b>. In particular


@@ -325,8 +325,8 @@
        since 1970-01-01 00:00:00 UTC. For example:
           date:@&lt;initial-timestamp&gt;..@&lt;final-timestamp&gt;
 
        since 1970-01-01 00:00:00 UTC. For example:
           date:@&lt;initial-timestamp&gt;..@&lt;final-timestamp&gt;
 

-       Currently, spaces in range  expressions  are  not  supported.  You  can
-       replace the spaces with &apos;_&apos;, or (in most cases) &apos;-&apos;, or (in some cases)
+       Currently, spaces in range expressions are not supported. You  can  re‐
+       place  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.
 
        leave the spaces out altogether. Examples in this man page  use  spaces
        for clarity.
 


@@ -352,8 +352,8 @@
        Units can be abbreviated to any length, with  the  otherwise  ambiguous
        single m being m for minutes and M for months.
 
        Units can be abbreviated to any length, with  the  otherwise  ambiguous
        single m being m for minutes and M for months.
 

-       Number  can  also  be  written  out one, two, ..., ten, dozen, hundred.
-       Additionally, the unit may be preceded by &quot;last&quot; or &quot;this&quot; (e.g., &quot;last
+       Number can also be written out one, two, ..., ten, dozen, hundred.  Ad‐
+       ditionally, the unit may be preceded by &quot;last&quot; or &quot;this&quot;  (e.g.,  &quot;last

        week&quot; or &quot;this month&quot;).
 
        When  combined  with absolute date and time, the relative date and time
        week&quot; or &quot;this month&quot;).
 
        When  combined  with absolute date and time, the relative date and time


@@ -365,40 +365,40 @@
 
 <h3> &nbsp; Supported absolute time formats</h3>
 <pre>
 
 <h3> &nbsp; Supported absolute time formats</h3>
 <pre>

-       · H[H]:MM[:SS] [(am|a.m.|pm|p.m.)]
+       • H[H]:MM[:SS] [(am|a.m.|pm|p.m.)]

 
 

-       · H[H] (am|a.m.|pm|p.m.)
+       • H[H] (am|a.m.|pm|p.m.)

 
 

-       · HHMMSS
+       • HHMMSS

 
 

-       · now
+       • now

 
 

-       · noon
+       • noon

 
 

-       · midnight
+       • midnight

 
 

-       · Examples: 17:05, 5pm
+       • Examples: 17:05, 5pm

 </pre>
 
 <h3> &nbsp; Supported absolute date formats</h3>
 <pre>
 </pre>
 
 <h3> &nbsp; Supported absolute date formats</h3>
 <pre>

-       · YYYY-MM[-DD]
+       • YYYY-MM[-DD]

 
 

-       · DD-MM[-[YY]YY]
+       • DD-MM[-[YY]YY]

 
 

-       · MM-YYYY
+       • MM-YYYY

 
 

-       · M[M]/D[D][/[YY]YY]
+       • M[M]/D[D][/[YY]YY]

 
 

-       · M[M]/YYYY
+       • M[M]/YYYY

 
 

-       · D[D].M[M][.[YY]YY]
+       • D[D].M[M][.[YY]YY]

 
 

-       · D[D][(st|nd|rd|th)] Mon[thname] [YYYY]
+       • D[D][(st|nd|rd|th)] Mon[thname] [YYYY]

 
 

-       · Mon[thname] D[D][(st|nd|rd|th)] [YYYY]
+       • Mon[thname] D[D][(st|nd|rd|th)] [YYYY]

 
 

-       · Wee[kday]
+       • Wee[kday]

 
        Month names can be abbreviated at three or more characters.
 
 
        Month names can be abbreviated at three or more characters.
 


@@ -409,9 +409,9 @@
 
 <h3> &nbsp; Time zones</h3>
 <pre>
 
 <h3> &nbsp; Time zones</h3>
 <pre>

-       · (+|-)HH:MM
+       • (+|-)HH:MM

 
 

-       · (+|-)HH[MM]
+       • (+|-)HH[MM]

 
        Some time zone codes, e.g. UTC, EET.
 </pre>
 
        Some time zone codes, e.g. UTC, EET.
 </pre>


@@ -431,7 +431,7 @@
 
 <h2>COPYRIGHT</h2>
 <pre>
 
 <h2>COPYRIGHT</h2>
 <pre>

-       2009-2020, Carl Worth and many others
+       2009-2021, Carl Worth and many others

 </pre>
 
 </pre>
 

-<h2>0.31</h2>
+<h2>0.32</h2>