From 972d44d9cb20af9363eb251fc6e748912ad0ca32 Mon Sep 17 00:00:00 2001 From: Tomi Ollila Date: Tue, 4 Oct 2016 11:30:07 +0300 Subject: [PATCH] 0.23 namual pages --- manpages.mdwn | 3 + manpages/notmuch-1.mdwn | 55 ++++++++-------- manpages/notmuch-address-1.mdwn | 24 +++---- manpages/notmuch-compact-1.mdwn | 2 +- manpages/notmuch-config-1.mdwn | 10 +-- manpages/notmuch-count-1.mdwn | 2 +- manpages/notmuch-dump-1.mdwn | 25 +++++--- manpages/notmuch-hooks-5.mdwn | 4 +- manpages/notmuch-insert-1.mdwn | 10 +-- manpages/notmuch-new-1.mdwn | 2 +- manpages/notmuch-reply-1.mdwn | 62 +++++++++---------- manpages/notmuch-restore-1.mdwn | 20 +++--- manpages/notmuch-search-1.mdwn | 2 +- manpages/notmuch-search-terms-7.mdwn | 93 +++++++++++++++------------- manpages/notmuch-show-1.mdwn | 2 +- manpages/notmuch-tag-1.mdwn | 2 +- 16 files changed, 171 insertions(+), 147 deletions(-) diff --git a/manpages.mdwn b/manpages.mdwn index 137f5b9..9b65cce 100644 --- a/manpages.mdwn +++ b/manpages.mdwn @@ -20,3 +20,6 @@ Manual page index The manual pages are licensed under [the GNU General Public License](https://www.gnu.org/licenses/gpl.txt), either version 3.0 or at your option any later version. + +

0.23

+ diff --git a/manpages/notmuch-1.mdwn b/manpages/notmuch-1.mdwn index 36883d9..6fe3db3 100644 --- a/manpages/notmuch-1.mdwn +++ b/manpages/notmuch-1.mdwn @@ -31,7 +31,7 @@ it does not provide the most convenient interface for that functional‐ ity. More sophisticated interfaces are expected to be built on top of either the command-line interface, or more likely, on top of the not‐ - much library interface. See https://notmuchmail.org for more about + much library interface. See https://notmuchmail.org for more about alternate interfaces to notmuch. The emacs-based interface to notmuch (available under emacs/ in the Notmuch source distribution) is probably the most widely used at this time. @@ -49,7 +49,7 @@ Print the installed version of notmuch, and exit. --config=FILE - Specify the configuration file to use. This overrides any + Specify the configuration file to use. This overrides any configuration file specified by ${NOTMUCH_CONFIG}. --uuid=HEX @@ -68,51 +68,51 @@

  SETUP

-       The  notmuch  setup command is used to configure Notmuch for first use,
+       The notmuch setup command is used to configure Notmuch for  first  use,
        (or to reconfigure it later).
 
-       The setup command will prompt for your full name,  your  primary  email
-       address,  any alternate email addresses you use, and the directory con‐
+       The  setup  command  will prompt for your full name, your primary email
+       address, any alternate email addresses you use, and the directory  con‐
        taining your email archives. Your answers will be written to a configu‐
-       ration  file in ${NOTMUCH_CONFIG} (if set) or ${HOME}/.notmuch-config .
+       ration file in ${NOTMUCH_CONFIG} (if set) or ${HOME}/.notmuch-config  .
        This configuration file will be created with descriptive comments, mak‐
-       ing  it  easy to edit by hand later to change the configuration. Or you
+       ing it easy to edit by hand later to change the configuration.  Or  you
        can run notmuch setup again to change the configuration.
 
-       The mail directory you specify can contain any number  of  sub-directo‐
+       The  mail  directory you specify can contain any number of sub-directo‐
        ries and should primarily contain only files with individual email mes‐
-       sages (eg. maildir or mh archives are perfect).  If  there  are  other,
-       non-email  files  (such  as indexes maintained by other email programs)
+       sages  (eg.  maildir  or  mh archives are perfect). If there are other,
+       non-email files (such as indexes maintained by  other  email  programs)
        then notmuch will do its best to detect those and ignore them.
 
-       Mail storage that uses mbox format, (where one mbox file contains  many
-       messages),  will not work with notmuch. If that's how your mail is cur‐
+       Mail  storage that uses mbox format, (where one mbox file contains many
+       messages), will not work with notmuch. If that's how your mail is  cur‐
        rently stored, it is recommended you first convert it to maildir format
        with a utility such as mb2md before running notmuch setup .
 
-       Invoking  notmuch  with no command argument will run setup if the setup
+       Invoking notmuch with no command argument will run setup if  the  setup
        command has not previously been completed.

  OTHER COMMANDS

-       Several of the notmuch commands accept search terms with a common  syn‐
+       Several  of the notmuch commands accept search terms with a common syn‐
        tax. See notmuch-search-terms(7) for more details on the supported syn‐
        tax.
 
-       The search, show, address and count commands  are  used  to  query  the
+       The  search,  show,  address  and  count commands are used to query the
        email database.
 
-       The  reply  command  is  useful  for  preparing a template for an email
+       The reply command is useful for  preparing  a  template  for  an  email
        reply.
 
        The tag command is the only command available for manipulating database
        contents.
 
-       The  dump  and restore commands can be used to create a textual dump of
+       The dump and restore commands can be used to create a textual  dump  of
        email tags for backup purposes, and to restore from that dump.
 
-       The config command can be used to get or set settings  in  the  notmuch
+       The  config  command  can be used to get or set settings in the notmuch
        configuration file.
@@ -122,25 +122,26 @@ of notmuch. NOTMUCH_CONFIG - Specifies the location of the notmuch configuration file. Not‐ - much will use ${HOME}/.notmuch-config if this variable is not + Specifies the location of the notmuch configuration file. Not‐ + much will use ${HOME}/.notmuch-config if this variable is not set. NOTMUCH_TALLOC_REPORT - Location to write a talloc memory usage report. See tal- + Location to write a talloc memory usage report. See tal- loc_enable_leak_report_full in talloc(3) for more information. NOTMUCH_DEBUG_QUERY - If set to a non-empty value, the notmuch library will print (to + If set to a non-empty value, the notmuch library will print (to stderr) Xapian queries it constructs.

SEE ALSO

-       notmuch-config(1), notmuch-count(1), notmuch-dump(1), notmuch-hooks(5),
-       notmuch-insert(1),      notmuch-new(1),      notmuch-reply(1),     not‐
-       much-restore(1),   notmuch-search(1),   notmuch-search-terms(7),   not‐
-       much-show(1), notmuch-tag(1), notmuch-address(1)
+       notmuch-address(1),    notmuch-compact(1),    notmuch-config(1),   not‐
+       much-count(1),  notmuch-dump(1),  notmuch-hooks(5),  notmuch-insert(1),
+       notmuch-new(1),      notmuch-reply(1),     notmuch-restore(1),     not‐
+       much-search(1),    notmuch-search-terms(7),    notmuch-show(1),    not‐
+       much-tag(1)
 
        The notmuch website: https://notmuchmail.org
@@ -165,4 +166,4 @@ 2009-2016, Carl Worth and many others -

0.22.1

+

0.23

diff --git a/manpages/notmuch-address-1.mdwn b/manpages/notmuch-address-1.mdwn index d3cd26e..f3f5fcd 100644 --- a/manpages/notmuch-address-1.mdwn +++ b/manpages/notmuch-address-1.mdwn @@ -74,12 +74,12 @@ is specified, include all variants in the count. --sort=(newest-first|oldest-first) - This option can be used to present results in either chrono‐ - logical order (oldest-first) or reverse chronological order + This option can be used to present results in either chrono‐ + logical order (oldest-first) or reverse chronological order (newest-first). - By default, results will be displayed in reverse chronologi‐ - cal order, (that is, the newest results will be displayed + By default, results will be displayed in reverse chronologi‐ + cal order, (that is, the newest results will be displayed first). However, if either --output=count or --deduplicate=address is @@ -88,14 +88,14 @@ --exclude=(true|false) A message is called "excluded" if it matches at least one tag - in search.tag_exclude that does not appear explicitly in the - search terms. This option specifies whether to omit excluded + in search.tag_exclude that does not appear explicitly in the + search terms. This option specifies whether to omit excluded messages in the search process. - The default value, true, prevents excluded messages from + The default value, true, prevents excluded messages from matching the search terms. - false allows excluded messages to match search terms and + false allows excluded messages to match search terms and appear in displayed results. @@ -110,9 +110,9 @@

SEE ALSO

-       notmuch(1),  notmuch-config(1), notmuch-count(1), notmuch-dump(1), not‐
-       much-hooks(5),  notmuch-insert(1),  notmuch-new(1),   notmuch-reply(1),
-       notmuch-restore(1),   notmuch-search-terms(7),   notmuch-show(1),  not‐
+       notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1),  not‐
+       much-hooks(5),   notmuch-insert(1),  notmuch-new(1),  notmuch-reply(1),
+       notmuch-restore(1),  notmuch-search-terms(7),   notmuch-show(1),   not‐
        much-tag(1), notmuch-search(1)
@@ -126,4 +126,4 @@ 2009-2016, Carl Worth and many others -

0.22.1

+

0.23

diff --git a/manpages/notmuch-compact-1.mdwn b/manpages/notmuch-compact-1.mdwn index 445f0bf..a070972 100644 --- a/manpages/notmuch-compact-1.mdwn +++ b/manpages/notmuch-compact-1.mdwn @@ -64,4 +64,4 @@ 2009-2016, Carl Worth and many others -

0.22.1

+

0.23

diff --git a/manpages/notmuch-config-1.mdwn b/manpages/notmuch-config-1.mdwn index d079c17..820d10f 100644 --- a/manpages/notmuch-config-1.mdwn +++ b/manpages/notmuch-config-1.mdwn @@ -146,15 +146,15 @@ of notmuch. NOTMUCH_CONFIG - Specifies the location of the notmuch configuration file. Not‐ - much will use ${HOME}/.notmuch-config if this variable is not + Specifies the location of the notmuch configuration file. Not‐ + much will use ${HOME}/.notmuch-config if this variable is not set.

SEE ALSO

-       notmuch(1),  notmuch-count(1),  notmuch-dump(1), notmuch-hooks(5), not‐
-       much-insert(1), notmuch-new(1),  notmuch-reply(1),  notmuch-restore(1),
+       notmuch(1), notmuch-count(1), notmuch-dump(1),  notmuch-hooks(5),  not‐
+       much-insert(1),  notmuch-new(1),  notmuch-reply(1), notmuch-restore(1),
        notmuch-search(1),   notmuch-search-terms(7),   notmuch-show(1),   not‐
        much-tag(1)
@@ -169,4 +169,4 @@ 2009-2016, Carl Worth and many others -

0.22.1

+

0.23

diff --git a/manpages/notmuch-count-1.mdwn b/manpages/notmuch-count-1.mdwn index 1007fa8..73028d8 100644 --- a/manpages/notmuch-count-1.mdwn +++ b/manpages/notmuch-count-1.mdwn @@ -77,4 +77,4 @@ 2009-2016, Carl Worth and many others -

0.22.1

+

0.23

diff --git a/manpages/notmuch-dump-1.mdwn b/manpages/notmuch-dump-1.mdwn index 5239cc5..7c6e86a 100644 --- a/manpages/notmuch-dump-1.mdwn +++ b/manpages/notmuch-dump-1.mdwn @@ -68,21 +68,28 @@ characters. Note also that tags with spaces will not be correctly restored with this format. - --include=(config|tags) + --include=(config|properties|tags) Control what kind of metadata is included in the output. config Output configuration data stored in the database. Each line - starts with "#@ ", followed by a space seperated key-value + starts with "#@ ", followed by a space separated key-value pair. Both key and value are hex encoded if needed. + properties + Output per-message (key,value) metadata. Each line starts + with "#= ", followed by a message id, and a space separated + list of key=value pairs. pair. Ids, keys and values are hex + encoded if needed. + tags - Output per-message metadata, namely tags. See format above - for description of the output. + Output per-message boolean metadata, namely tags. See format + above for description of the output. - The default is to include both tags and configuration informa‐ - tion. As of version 2 of the dump format, there is a header line - of the following form + The default is to include all available types of data. The + option can be specified multiple times to select some subset. As + of version 2 of the dump format, there is a header line of the + following form #notmuch-dump <format>:<version> <included> @@ -95,7 +102,7 @@

SEE ALSO

        notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-hooks(5), not‐
-       much-insert(1),  notmuch-new(1),  notmuch-reply(1), notmuch-restore(1),
+       much-insert(1), notmuch-new(1),  notmuch-reply(1),  notmuch-restore(1),
        notmuch-search(1),   notmuch-search-terms(7),   notmuch-show(1),   not‐
        much-tag(1)
@@ -110,4 +117,4 @@ 2009-2016, Carl Worth and many others -

0.22.1

+

0.23

diff --git a/manpages/notmuch-hooks-5.mdwn b/manpages/notmuch-hooks-5.mdwn index 1fac540..9a26238 100644 --- a/manpages/notmuch-hooks-5.mdwn +++ b/manpages/notmuch-hooks-5.mdwn @@ -41,7 +41,7 @@ This hook is invoked by the insert command after the message has been delivered, added to the database, and initial tags have been applied. The hook will not be run if there have been any - errors during the message delivery; what is regarded as succes‐ + errors during the message delivery; what is regarded as success‐ ful delivery depends on the --keep option. Typically this hook is used to perform additional query-based @@ -66,4 +66,4 @@ 2009-2016, Carl Worth and many others -

0.22.1

+

0.23

diff --git a/manpages/notmuch-insert-1.mdwn b/manpages/notmuch-insert-1.mdwn index 54cfd13..68626ab 100644 --- a/manpages/notmuch-insert-1.mdwn +++ b/manpages/notmuch-insert-1.mdwn @@ -45,7 +45,7 @@ --keep Keep the message file if indexing fails, and keep the message indexed if applying tags or maildir flag synchronization fails. Ignore these errors and return exit status 0 to indi‐ - cate succesful mail delivery. + cate successful mail delivery. --no-hooks Prevent hooks from being run. @@ -53,9 +53,9 @@

EXIT STATUS

-       This command returns exit status 0 on succesful mail delivery, non-zero
-       otherwise.  The  default  is  to  indicate  failed mail delivery on any
-       errors, including message file  delivery  to  the  filesystem,  message
+       This command  returns  exit  status  0  on  successful  mail  delivery,
+       non-zero  otherwise. The default is to indicate failed mail delivery on
+       any errors, including message file delivery to the filesystem,  message
        indexing  to Notmuch database, changing tags, and synchronizing tags to
        maildir flags. The --keep option may be used to settle  for  successful
        message file delivery.
@@ -81,4 +81,4 @@
        2009-2016, Carl Worth and many others
-

0.22.1

+

0.23

diff --git a/manpages/notmuch-new-1.mdwn b/manpages/notmuch-new-1.mdwn index 7b794a6..d6d75f6 100644 --- a/manpages/notmuch-new-1.mdwn +++ b/manpages/notmuch-new-1.mdwn @@ -63,4 +63,4 @@ 2009-2016, Carl Worth and many others -

0.22.1

+

0.23

diff --git a/manpages/notmuch-reply-1.mdwn b/manpages/notmuch-reply-1.mdwn index 317a760..19639bb 100644 --- a/manpages/notmuch-reply-1.mdwn +++ b/manpages/notmuch-reply-1.mdwn @@ -23,12 +23,12 @@ of the current user's email addresses (as configured in primary_mail or other_email in the .notmuch-config file) in the recipient list. - It also builds a suitable new subject, including Re: at the front (if - not already present), and adding the message IDs of the messages being - replied to to the References list and setting the In-Reply-To: field + It also builds a suitable new subject, including Re: at the front (if + not already present), and adding the message IDs of the messages being + replied to to the References list and setting the In-Reply-To: field correctly. - Finally, the original contents of the emails are quoted by prefixing + Finally, the original contents of the emails are quoted by prefixing each line with '> ' and included in the body. The resulting message template is output to stdout. @@ -37,26 +37,26 @@ --format=(default|json|sexp|headers-only) default - Includes subject and quoted message body as an RFC 2822 + Includes subject and quoted message body as an RFC 2822 message. - json Produces JSON output containing headers for a reply mes‐ - sage and the contents of the original message. This out‐ - put can be used by a client to create a reply message + json Produces JSON output containing headers for a reply mes‐ + sage and the contents of the original message. This out‐ + put can be used by a client to create a reply message intelligently. - sexp Produces S-Expression output containing headers for a - reply message and the contents of the original message. - This output can be used by a client to create a reply + sexp Produces S-Expression output containing headers for a + reply message and the contents of the original message. + This output can be used by a client to create a reply message intelligently. headers-only - Only produces In-Reply-To, References, To, Cc, and Bcc + Only produces In-Reply-To, References, To, Cc, and Bcc headers. --format-version=N - Use the specified structured output format version. This is - intended for programs that invoke notmuch(1) internally. If + Use the specified structured output format version. This is + intended for programs that invoke notmuch(1) internally. If omitted, the latest supported version will be used. --reply-to=(all|sender) @@ -64,32 +64,32 @@ all (default) Replies to all addresses. - sender Replies only to the sender. If replying to user's own - message (Reply-to: or From: header is one of the user's + sender Replies only to the sender. If replying to user's own + message (Reply-to: or From: header is one of the user's configured email addresses), try To:, Cc:, and Bcc: head‐ - ers in this order, and copy values from the first that + ers in this order, and copy values from the first that contains something other than only the user's addresses. --decrypt - Decrypt any MIME encrypted parts found in the selected con‐ + Decrypt any MIME encrypted parts found in the selected con‐ tent (ie. "multipart/encrypted" parts). Status of the decryp‐ - tion will be reported (currently only supported with --for‐ - mat=json and --format=sexp) and on successful decryption the - multipart/encrypted part will be replaced by the decrypted + tion will be reported (currently only supported with --for‐ + mat=json and --format=sexp) and on successful decryption the + multipart/encrypted part will be replaced by the decrypted content. - Decryption expects a functioning gpg-agent(1) to provide any + Decryption expects a functioning gpg-agent(1) to provide any needed credentials. Without one, the decryption will fail. - See notmuch-search-terms(7) for details of the supported syntax for + See notmuch-search-terms(7) for details of the supported syntax for <search-terms>. - Note: It is most common to use notmuch reply with a search string - matching a single message, (such as id:<message-id>), but it can be + Note: It is most common to use notmuch reply with a search string + matching a single message, (such as id:<message-id>), but it can be useful to reply to several messages at once. For example, when a series - of patches are sent in a single thread, replying to the entire thread - allows for the reply to comment on issues found in multiple patches. - The default format supports replying to multiple messages at once, but + of patches are sent in a single thread, replying to the entire thread + allows for the reply to comment on issues found in multiple patches. + The default format supports replying to multiple messages at once, but the JSON and S-Expression formats do not. @@ -104,8 +104,8 @@

SEE ALSO

-       notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1),  not‐
-       much-hooks(5),  notmuch-insert(1),  notmuch-new(1), notmuch-restore(1),
+       notmuch(1),  notmuch-config(1), notmuch-count(1), notmuch-dump(1), not‐
+       much-hooks(5), notmuch-insert(1),  notmuch-new(1),  notmuch-restore(1),
        notmuch-search(1),   notmuch-search-terms(7),   notmuch-show(1),   not‐
        much-tag(1)
@@ -120,4 +120,4 @@ 2009-2016, Carl Worth and many others -

0.22.1

+

0.23

diff --git a/manpages/notmuch-restore-1.mdwn b/manpages/notmuch-restore-1.mdwn index 98e46d8..d165877 100644 --- a/manpages/notmuch-restore-1.mdwn +++ b/manpages/notmuch-restore-1.mdwn @@ -54,20 +54,26 @@ batch-tag format contains no parentheses, should be accurate. - --include=(config|tags) + --include=(config|properties|tags) Control what kind of metadata is restored. config Restore configuration data to the database. Each configu‐ - ration line starts with "#@ ", followed by a space seper‐ - ated key-value pair. Both key and value are hex encoded + ration line starts with "#@ ", followed by a space sepa‐ + rated key-value pair. Both key and value are hex encoded if needed. + properties + Output per-message (key,value) metadata. Each line + starts with "#= ", followed by a message id, and a space + separated list of key=value pairs. pair. Ids, keys and + values are hex encoded if needed. + tags - Output per-message metadata, namely tags. See format + Output per-message metadata, namely tags. See format above for more details. - The default is to restore both tags and configuration informa‐ - tion + The default is to restore all available types of data. The + option can be specified multiple times to select some subset. --input=<filename> Read input from given file instead of stdin. @@ -98,4 +104,4 @@ 2009-2016, Carl Worth and many others -

0.22.1

+

0.23

diff --git a/manpages/notmuch-search-1.mdwn b/manpages/notmuch-search-1.mdwn index 38ef134..6a0a8a0 100644 --- a/manpages/notmuch-search-1.mdwn +++ b/manpages/notmuch-search-1.mdwn @@ -166,4 +166,4 @@ 2009-2016, Carl Worth and many others -

0.22.1

+

0.23

diff --git a/manpages/notmuch-search-terms-7.mdwn b/manpages/notmuch-search-terms-7.mdwn index c137734..21ba240 100644 --- a/manpages/notmuch-search-terms-7.mdwn +++ b/manpages/notmuch-search-terms-7.mdwn @@ -61,6 +61,8 @@ · query:<name> + · property:<key>=<value> + The from: prefix is used to match the name or address of the sender of an email message. @@ -136,27 +138,32 @@ The query: prefix allows queries to refer to previously saved queries added with notmuch-config(1). Named queries are only available if not‐ much is built with Xapian Field Processors (see below). + + The property: prefix searches for messages with a particular + <key>=<value> property pair. Properties are used internally by notmuch + (and extensions) to add metadata to messages. A given key can be + present on a given message with several different values.

  Operators

-       In addition to individual terms, multiple terms can  be  combined  with
-       Boolean  operators (and, or, not, and xor). Each term in the query will
-       be implicitly connected by a logical AND if  no  explicit  operator  is
-       provided  (except  that  terms  with a common prefix will be implicitly
-       combined with OR).  The  shorthand  '-<term>'  can  be  used  for  'not
+       In  addition  to  individual terms, multiple terms can be combined with
+       Boolean operators (and, or, not, and xor). Each term in the query  will
+       be  implicitly  connected  by  a logical AND if no explicit operator is
+       provided (except that terms with a common  prefix  will  be  implicitly
+       combined  with  OR).   The  shorthand  '-<term>'  can  be used for 'not
        <term>' but unfortunately this does not work at the start of an expres‐
-       sion.  Parentheses can also be used to control the combination  of  the
+       sion.   Parentheses  can also be used to control the combination of the
        Boolean operators, but will have to be protected from interpretation by
        the shell, (such as by putting quotation marks around any parenthesized
        expression).
 
-       In  addition to the standard boolean operators, Xapian provides several
+       In addition to the standard boolean operators, Xapian provides  several
        operators specific to text searching.
 
           notmuch search term1 NEAR term2
 
-       will return results where term1  is  within  10  words  of  term2.  The
+       will  return  results  where  term1  is  within  10 words of term2. The
        threshold can be set like this:
 
           notmuch search term1 NEAR/2 term2
@@ -166,7 +173,7 @@
           notmuch search term1 ADJ term2
 
        will return results where term1 is within 10 words of term2, but in the
-       same order as in the query. The threshold can be set the same  as  with
+       same  order  as in the query. The threshold can be set the same as with
        NEAR:
 
           notmuch search term1 ADJ/7 term2
@@ -180,31 +187,31 @@
           notmuch search details
           notmuch search detail
 
-       will  all  return identical results, because Xapian first "reduces" the
+       will all return identical results, because Xapian first  "reduces"  the
        term to the common stem (here 'detail') and then performs the search.
 
-       There are two ways to turn this off: a search for  a  capitalized  word
-       will  be performed unstemmed, so that one can search for "John" and not
-       get results for "Johnson"; phrase  searches  are  also  unstemmed  (see
-       below  for details).  Stemming is currently only supported for English.
+       There  are  two  ways to turn this off: a search for a capitalized word
+       will be performed unstemmed, so that one can search for "John" and  not
+       get  results  for  "Johnson";  phrase  searches are also unstemmed (see
+       below for details).  Stemming is currently only supported for  English.
        Searches for words in other languages will be performed unstemmed.

  Wildcards

-       It is possible to use a trailing  '*'  as  a  wildcard.  A  search  for
+       It  is  possible  to  use  a  trailing  '*' as a wildcard. A search for
        'wildc*' will match 'wildcard', 'wildcat', etc.

  Boolean and Probabilistic Prefixes

-       Xapian  (and  hence  notmuch)  prefixes  are either boolean, supporting
-       exact matches like "tag:inbox"  or  probabilistic,  supporting  a  more
+       Xapian (and hence notmuch)  prefixes  are  either  boolean,  supporting
+       exact  matches  like  "tag:inbox"   or probabilistic, supporting a more
        flexible term based searching. The prefixes currently supported by not‐
        much are as follows.
 
        Boolean
-              tag:, id:, thread:, folder:, path:
+              tag:, id:, thread:, folder:, path:, property:
 
        Probabilistic
               from:, to:, subject:, attachment:, mimetype:
@@ -212,10 +219,10 @@
 
 
   Terms and phrases

 
-       In general Xapian distinguishes between lists  of  terms  and  phrases.
+       In  general  Xapian  distinguishes  between lists of terms and phrases.
        Phrases are indicated by double quotes (but beware you probably need to
-       protect those from your shell) and insist that  those  unstemmed  words
-       occur  in  that  order. One useful, but initially surprising feature is
+       protect  those  from  your shell) and insist that those unstemmed words
+       occur in that order. One useful, but initially  surprising  feature  is
        that the following are equivalant ways to write the same phrase.
 
        · "a list of words"
@@ -244,11 +251,11 @@
 
 
DATE AND TIME SEARCH

 
-       notmuch  understands a variety of standard and natural ways of express‐
+       notmuch understands a variety of standard and natural ways of  express‐
        ing dates and times, both in absolute terms ("2012-10-24") and in rela‐
-       tive  terms ("yesterday"). Any number of relative terms can be combined
-       ("1 hour 25 minutes") and an absolute date/time can  be  combined  with
-       relative  terms  to  further adjust it. A non-exhaustive description of
+       tive terms ("yesterday"). Any number of relative terms can be  combined
+       ("1  hour  25  minutes") and an absolute date/time can be combined with
+       relative terms to further adjust it. A  non-exhaustive  description  of
        the syntax supported for absolute and relative terms is given below.
 

 
@@ -256,23 +263,23 @@
 
        date:<since>..<until>
 
-       The above expression  restricts  the  results  to  only  messages  from
+       The  above  expression  restricts  the  results  to  only messages from
        <since> to <until>, based on the Date: header.
 
-       <since>  and <until> can describe imprecise times, such as "yesterday".
-       In this case, <since> is taken as the earliest time it  could  describe
+       <since> and <until> can describe imprecise times, such as  "yesterday".
+       In  this  case, <since> is taken as the earliest time it could describe
        (the beginning of yesterday) and <until> is taken as the latest time it
-       could describe (the end of yesterday). Similarly,  date:january..febru‐
+       could  describe (the end of yesterday). Similarly, date:january..febru‐
        ary matches from the beginning of January to the end of February.
 
-       date:<expr>..!  can be used as a shorthand for date:<expr>..<expr>. The
-       expansion takes place before interpretation,  and  thus,  for  example,
-       date:monday..!  matches  from  the beginning of Monday until the end of
-       Monday.  With Xapian Field Processor  support  (see  below),  non-range
-       date  queries such as date:yesterday will work, but otherwise will give
+       date:<expr>..! can be used as a shorthand for date:<expr>..<expr>.  The
+       expansion  takes  place  before  interpretation, and thus, for example,
+       date:monday..! matches from the beginning of Monday until  the  end  of
+       Monday.   With  Xapian  Field  Processor 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
+       Currently,  we  do  not  support  spaces  in range expressions. You can
        replace the spaces with '_', or (in most cases) '-', or (in some cases)
        leave  the  spaces out altogether. Examples in this man page use spaces
        for clarity.
@@ -290,15 +297,15 @@
 
        All refer to past, can be repeated and will be accumulated.
 
-       Units  can  be  abbreviated to any length, with the otherwise ambiguous
+       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.
+       Number  can  also  be  written  out one, two, ..., ten, dozen, hundred.
        Additionally, the unit may be preceded by "last" or "this" (e.g., "last
        week" or "this month").
 
-       When combined with absolute date and time, the relative date  and  time
-       specification  will  be  relative  from the specified absolute date and
+       When  combined  with absolute date and time, the relative date and time
+       specification will be relative from the  specified  absolute  date  and
        time.
 
        Examples: 5M2d, two weeks
@@ -359,9 +366,9 @@
 
 
XAPIAN FIELD PROCESSORS

 
-       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
+       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
@@ -390,4 +397,4 @@
        2009-2016, Carl Worth and many others
 

 
-
0.22.1

+
0.23

diff --git a/manpages/notmuch-show-1.mdwn b/manpages/notmuch-show-1.mdwn
index daf3b84..b9798c7 100644
--- a/manpages/notmuch-show-1.mdwn
+++ b/manpages/notmuch-show-1.mdwn
@@ -188,4 +188,4 @@
        2009-2016, Carl Worth and many others
 

 
-
0.22.1

+
0.23

diff --git a/manpages/notmuch-tag-1.mdwn b/manpages/notmuch-tag-1.mdwn
index f989972..ca9a9a7 100644
--- a/manpages/notmuch-tag-1.mdwn
+++ b/manpages/notmuch-tag-1.mdwn
@@ -117,4 +117,4 @@
        2009-2016, Carl Worth and many others
 

 
-
0.22.1

+
0.23

-- 
2.43.0