From: Tomi Ollila Date: Sat, 3 Aug 2013 20:33:08 +0000 (+0300) Subject: Update news & manpages to notmuch version 0.16 X-Git-Url: https://git.cworth.org/git?p=obsolete%2Fnotmuch-wiki;a=commitdiff_plain;h=ad04c8c6b3d8c29a905d9f5f92256fc2bd64be5e Update news & manpages to notmuch version 0.16 Executed ../notmuch/devel/news2wiki.pl ../notmuch/NEWS news ../notmuch/devel/man-to-mdwn.pl ../notmuch/man/ . git add manpages/notmuch-insert-1.mdwn git add news/release-0.16.mdwn git commit -a in debootstrapped Debian 7 (Wheezy) inside lxc container running in Fedora 19. --- diff --git a/manpages.mdwn b/manpages.mdwn index 6bb01fa..8c49ec4 100644 --- a/manpages.mdwn +++ b/manpages.mdwn @@ -5,6 +5,7 @@ Manual page index * notmuch-config(1) - access notmuch configuration file * notmuch-count(1) - count messages matching the given search terms * notmuch-dump(1) - creates a plain-text dump of the tags of each message +* notmuch-insert(1) - add a message to the maildir and notmuch database * notmuch-new(1) - incorporate new mail into the notmuch database * notmuch-reply(1) - constructs a reply template for a set of messages * notmuch-restore(1) - restores the tags from the given file (see notmuch dump) diff --git a/manpages/notmuch-1.mdwn b/manpages/notmuch-1.mdwn index 131258d..5359098 100644 --- a/manpages/notmuch-1.mdwn +++ b/manpages/notmuch-1.mdwn @@ -7,7 +7,7 @@

SYNOPSIS

-       notmuch command [args ...]
+       notmuch [option ...] command [arg ...]

DESCRIPTION

@@ -37,55 +37,73 @@ the most widely used at this time. +

OPTIONS

+
+       Supported global options for notmuch include
+
+           --help
+
+               Print a synopsis of available commands and exit.
+
+           --version
+
+               Print the installed version of notmuch, and exit.
+
+           --config=FILE
+
+               Specify the configuration file to use. This overrides any  con-
+               figuration file specified by ${NOTMUCH_CONFIG}.
+
+

COMMANDS

  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  and  count  commands  are  used  to query the email
-       database.
+       The search, show and count commands are used to query the  email  data-
+       base.
 
-       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 int the notmuch
+       The config command can be used to get or set settings int  the  notmuch
        configuration file.
@@ -95,16 +113,25 @@ 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- + 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 + stderr) Xapian queries it constructs.

SEE ALSO

        notmuch-config(1), notmuch-count(1), notmuch-dump(1), notmuch-hooks(5),
-       notmuch-new(1),    notmuch-reply(1),    notmuch-restore(1),    notmuch-
-       search(1), notmuch-search-terms(7), notmuch-show(1), notmuch-tag(1)
+       notmuch-insert(1),     notmuch-new(1),    notmuch-reply(1),    notmuch-
+       restore(1),   notmuch-search(1),   notmuch-search-terms(7),    notmuch-
+       show(1), notmuch-tag(1)
 
        The notmuch website: http://notmuchmail.org
@@ -119,4 +146,4 @@ (server: irc.freenode.net, channel: #notmuch). -

Notmuch 0.15.2

+

Notmuch 0.16

diff --git a/manpages/notmuch-config-1.mdwn b/manpages/notmuch-config-1.mdwn index d525018..bb2248a 100644 --- a/manpages/notmuch-config-1.mdwn +++ b/manpages/notmuch-config-1.mdwn @@ -112,9 +112,10 @@

SEE ALSO

-       notmuch(1),  notmuch-count(1),  notmuch-dump(1), notmuch-hooks(5), not-
-       much-new(1), notmuch-reply(1),  notmuch-restore(1),  notmuch-search(1),
-       notmuch-search-terms(7), notmuch-show(1), notmuch-tag(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), notmuch-
+       tag(1)
-

Notmuch 0.15.2

+

Notmuch 0.16

diff --git a/manpages/notmuch-count-1.mdwn b/manpages/notmuch-count-1.mdwn index 7efe493..8f7ed46 100644 --- a/manpages/notmuch-count-1.mdwn +++ b/manpages/notmuch-count-1.mdwn @@ -16,8 +16,8 @@ The number of matching messages (or threads) is output to stdout. - With no search terms, a count of all messages (or threads) in the - database will be displayed. + With no search terms, a count of all messages (or threads) in the data- + base will be displayed. See notmuch-search-terms(7) for details of the supported syntax for <search-terms>. @@ -39,13 +39,27 @@ Specify whether to omit messages matching search.tag_exclude from the count (the default) or not. + + --batch + + Read queries from a file (stdin by default), one per line, and + output the number of matching messages (or threads) to stdout, + one per line. On an empty input line the count of all messages + (or threads) in the database will be output. This option is not + compatible with specifying search terms on the command line. + + --input=<filename> + + Read input from given file, instead of from stdin. Implies + --batch.

SEE ALSO

-       notmuch(1),  notmuch-config(1), notmuch-dump(1), notmuch-hooks(5), not-
-       much-new(1), notmuch-reply(1),  notmuch-restore(1),  notmuch-search(1),
-       notmuch-search-terms(7), notmuch-show(1), notmuch-tag(1)
+       notmuch(1), notmuch-config(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),  notmuch-
+       tag(1)
-

Notmuch 0.15.2

+

Notmuch 0.16

diff --git a/manpages/notmuch-dump-1.mdwn b/manpages/notmuch-dump-1.mdwn index 2f4db7f..76eac67 100644 --- a/manpages/notmuch-dump-1.mdwn +++ b/manpages/notmuch-dump-1.mdwn @@ -27,7 +27,9 @@ Notmuch restore supports two plain text dump formats, both with one message-id per line, followed by a list of tags. - sup The sup dump file format is specifically chosen to be compati- + sup + + The sup dump file format is specifically chosen to be compati- ble with the format of files produced by sup-dump. So if you've previously been using sup for mail, then the notmuch restore command provides you a way to import all of your tags @@ -52,12 +54,12 @@ Tags are hex-encoded by replacing every byte not matching the regex [A-Za-z0-9@=.,_+-] with %nn where nn is the two digit hex encoding. The message ID is a valid Xapian query, quoted using - Xapian boolean term quoting rules: if the ID contains whites- - pace or a close paren or starts with a double quote, it must be - enclosed in double quotes and double quotes inside the ID must - be doubled. The astute reader will notice this is a special - case of the batch input format for notmuch-tag(1); note that - the single message-id query is mandatory for notmuch- + Xapian boolean term quoting rules: if the ID contains white- + space or a close paren or starts with a double quote, it must + be enclosed in double quotes and double quotes inside the ID + must be doubled. The astute reader will notice this is a spe- + cial case of the batch input format for notmuch-tag(1); note + that the single message-id query is mandatory for notmuch- restore(1). With no search terms, a dump of all messages in the database will @@ -70,9 +72,10 @@

SEE ALSO

-       notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-hooks(5), not-
-       much-new(1),  notmuch-reply(1),  notmuch-restore(1), notmuch-search(1),
-       notmuch-search-terms(7), notmuch-show(1), notmuch-tag(1)
+       notmuch(1), notmuch-config(1), notmuch-count(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),  notmuch-
+       tag(1)
-

Notmuch 0.15.2

+

Notmuch 0.16

diff --git a/manpages/notmuch-hooks-5.mdwn b/manpages/notmuch-hooks-5.mdwn index 4546280..4e9f1c6 100644 --- a/manpages/notmuch-hooks-5.mdwn +++ b/manpages/notmuch-hooks-5.mdwn @@ -40,9 +40,10 @@

SEE ALSO

-       notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1),  not-
-       much-new(1),  notmuch-reply(1),  notmuch-restore(1), notmuch-search(1),
-       notmuch-search-terms(7), notmuch-show(1), notmuch-tag(1)
+       notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1),  not-
+       much-insert(1),  notmuch-new(1),  notmuch-reply(1), notmuch-restore(1),
+       notmuch-search(1), notmuch-search-terms(7),  notmuch-show(1),  notmuch-
+       tag(1)
-

Notmuch 0.15.2

+

Notmuch 0.16

diff --git a/manpages/notmuch-insert-1.mdwn b/manpages/notmuch-insert-1.mdwn new file mode 100644 index 0000000..8ccfda1 --- /dev/null +++ b/manpages/notmuch-insert-1.mdwn @@ -0,0 +1,63 @@ +

NOTMUCH-INSERT(1)

+ +

NAME

+
+       notmuch-insert - add a message to the maildir and notmuch database
+
+ +

SYNOPSIS

+
+       notmuch insert [options] [ +<tag>|-<tag> ... ]
+
+ +

DESCRIPTION

+
+       notmuch insert reads a message from standard input and delivers it into
+       the maildir directory given by configuration option database.path, then
+       incorporates  the message into the notmuch database.  It is an alterna-
+       tive to using a separate tool to deliver the message then running  not-
+       much new afterwards.
+
+       The  new message will be tagged with the tags specified by the new.tags
+       configuration option, then by operations specified on the command-line:
+       tags prefixed by '+' are added while those prefixed by '-' are removed.
+
+       If  the  new message is a duplicate of an existing message in the data-
+       base (it has same Message-ID), it will be added to the  maildir  folder
+       and notmuch database, but the tags will not be changed.
+
+       Option  arguments must appear before any tag operation arguments.  Sup-
+       ported options for insert include
+
+           --folder=<&lt;folder>&gt;
+
+               Deliver the message to the specified folder,  relative  to  the
+               top-level  directory  given by the value of database.path.  The
+               default is to deliver to the top-level directory.
+
+           --create-folder
+
+               Try to create the folder named by the --folder  option,  if  it
+               does  not  exist.   Otherwise the folder must already exist for
+               mail delivery to succeed.
+
+ +

EXIT STATUS

+
+       This command returns exit status 0  if  the  message  was  successfully
+       added  to  the mail directory, even if the message could not be indexed
+       and added to the notmuch database.  In the latter case, a warning  will
+       be printed to standard error but the message file will be left on disk.
+
+       If the message could not be written to disk then a non-zero exit status
+       is returned.
+
+ +

SEE ALSO

+
+       notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1),  not-
+       much-hooks(5), notmuch-reply(1), notmuch-restore(1), notmuch-search(1),
+       notmuch-search-terms(7), notmuch-show(1), notmuch-tag(1)
+
+ +

Notmuch 0.16

diff --git a/manpages/notmuch-new-1.mdwn b/manpages/notmuch-new-1.mdwn index 18169ff..60bd880 100644 --- a/manpages/notmuch-new-1.mdwn +++ b/manpages/notmuch-new-1.mdwn @@ -46,8 +46,9 @@

SEE ALSO

        notmuch(1),  notmuch-config(1), notmuch-count(1), notmuch-dump(1), not-
-       much-hooks(5), notmuch-reply(1), notmuch-restore(1), notmuch-search(1),
-       notmuch-search-terms(7), notmuch-show(1), notmuch-tag(1)
+       much-hooks(5), notmuch-insert(1), notmuch-reply(1), notmuch-restore(1),
+       notmuch-search(1),  notmuch-search-terms(7),  notmuch-show(1), notmuch-
+       tag(1)
-

Notmuch 0.15.2

+

Notmuch 0.16

diff --git a/manpages/notmuch-reply-1.mdwn b/manpages/notmuch-reply-1.mdwn index 41320dc..9dde8c4 100644 --- a/manpages/notmuch-reply-1.mdwn +++ b/manpages/notmuch-reply-1.mdwn @@ -79,8 +79,12 @@ Decrypt any MIME encrypted parts found in the selected con- tent (ie. "multipart/encrypted" parts). Status of the decryption will be reported (currently only supported with - --format=json and --format=sexp) and the multipart/encrypted - part will be replaced by the decrypted content. + --format=json and --format=sexp) and on successful decryp- + tion the multipart/encrypted part will be replaced by the + decrypted content. + + 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 <search-terms>. @@ -106,8 +110,9 @@

SEE ALSO

        notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1),  not-
-       much-hooks(5),  notmuch-new(1),  notmuch-restore(1), notmuch-search(1),
-       notmuch-search-terms(7), notmuch-show(1), notmuch-tag(1)
+       much-hooks(5),  notmuch-insert(1),  notmuch-new(1), notmuch-restore(1),
+       notmuch-search(1), notmuch-search-terms(7),  notmuch-show(1),  notmuch-
+       tag(1)
-

Notmuch 0.15.2

+

Notmuch 0.16

diff --git a/manpages/notmuch-restore-1.mdwn b/manpages/notmuch-restore-1.mdwn index a01cb38..8164f92 100644 --- a/manpages/notmuch-restore-1.mdwn +++ b/manpages/notmuch-restore-1.mdwn @@ -32,7 +32,9 @@ line specifying a message-id and a set of tags. For details of the actual formats, see notmuch-dump(1). - sup The sup dump file format is specifically chosen to be com- + sup + + The sup dump file format is specifically chosen to be com- patible with the format of files produced by sup-dump. So if you've previously been using sup for mail, then the not- much restore command provides you a way to import all of @@ -41,8 +43,8 @@ batch-tag The batch-tag dump format is intended to more robust - against malformed message-ids and tags containing whites- - pace or non-ascii(7) characters. See notmuch-dump(1) for + against malformed message-ids and tags containing white- + space or non-ascii(7) characters. See notmuch-dump(1) for details on this format. notmuch restore updates the maildir flags according to tag @@ -60,8 +62,9 @@

SEE ALSO

        notmuch(1),  notmuch-config(1), notmuch-count(1), notmuch-dump(1), not-
-       much-hooks(5),  notmuch-new(1),  notmuch-reply(1),   notmuch-search(1),
-       notmuch-search-terms(7), notmuch-show(1), notmuch-tag(1)
+       much-hooks(5),  notmuch-insert(1),  notmuch-new(1),   notmuch-reply(1),
+       notmuch-search(1),  notmuch-search-terms(7),  notmuch-show(1), notmuch-
+       tag(1)
-

Notmuch 0.15.2

+

Notmuch 0.16

diff --git a/manpages/notmuch-search-1.mdwn b/manpages/notmuch-search-1.mdwn index 11c3ba6..e8b6c27 100644 --- a/manpages/notmuch-search-1.mdwn +++ b/manpages/notmuch-search-1.mdwn @@ -82,8 +82,8 @@ --sort=(newest-first|oldest-first) This option can be used to present results in either chronolog- - ical order (oldest-first) or reverse chronological order - (newest-first). + ical order (oldest-first) or reverse chronological order (new- + est-first). Note: The thread order will be distinct between these two options (beyond being simply reversed). When sorting by old- @@ -103,13 +103,28 @@ Limit the number of displayed results to N. - --exclude=(true|false|flag) + --exclude=(true|false|all|flag) - Specify whether to omit messages matching search.tag_exclude - from the search results (the default) or not. The extra option - flag only has an effect when --output=summary In this case all - matching threads are returned but the "match count" is the num- - ber of matching non-excluded messages in the thread. + 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 + messages in the search process. + + The default value, true, prevents excluded messages from match- + ing the search terms. + + all additionally prevents excluded messages from appearing in + displayed results, in effect behaving as though the excluded + messages do not exist. + + false allows excluded messages to match search terms and appear + in displayed results. Excluded messages are still marked in the + relevant outputs. + + flag only has an effect when --output=summary. The output is + almost identical to false, but the "match count" is the number + of matching non-excluded messages in the thread, rather than + the number of matching messages.

EXIT STATUS

@@ -123,9 +138,10 @@

SEE ALSO

-       notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1),  not-
-       much-hooks(5),  notmuch-new(1),  notmuch-reply(1),  notmuch-restore(1),
-       notmuch-search-terms(7), notmuch-show(1), notmuch-tag(1)
+       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), notmuch-
+       tag(1)
-

Notmuch 0.15.2

+

Notmuch 0.16

diff --git a/manpages/notmuch-search-terms-7.mdwn b/manpages/notmuch-search-terms-7.mdwn index 634fde4..c4fe11d 100644 --- a/manpages/notmuch-search-terms-7.mdwn +++ b/manpages/notmuch-search-terms-7.mdwn @@ -96,59 +96,59 @@ <initial-timestamp>..<final-timestamp> - Each timestamp is a number representing the number of seconds since + Each timestamp is a number representing the number of seconds since 1970-01-01 00:00:00 UTC. - In addition to individual terms, multiple terms can be combined with - Boolean operators ( and, or, not , etc.). 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 + In addition to individual terms, multiple terms can be combined with + Boolean operators ( and, or, not , etc.). 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 until we get Xapian defect #402 fixed). - 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 + 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).

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.
 
            The range expression
 
                date:<since>..<until>
 
-               The  above  expression  restricts  the results to only messages
+               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 "yes-
-               terday".   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 yester-
+               terday".  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  yester-
                day). Similarly, date:january..february matches from the begin-
                ning of January to the end of February.
 
-               Currently,  we  do not support spaces in range expressions. You
+               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
+               some cases) leave the spaces out altogether. Examples  in  this
                man page use spaces for clarity.
 
                Open-ended ranges are supported (since Xapian 1.2.1), i.e. it's
-               possible  to  specify  date:..<until>  or date:<since>.. 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
+               possible to specify date:..<until>  or  date:<since>..  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 ".."  (for  example  date:yesterday)
-               won't  work,  as  it's not interpreted as a range expression at
-               all. You can achieve the expected  result  by  duplicating  the
-               expr  both  sides of ".."  (for example date:yesterday..yester-
+               Entering  date:expr  without  ".." (for example date:yesterday)
+               won't work, as it's not interpreted as a  range  expression  at
+               all.  You  can  achieve  the expected result by duplicating the
+               expr both sides of ".."  (for  example  date:yesterday..yester-
                day).
 
            Relative date and time
@@ -157,15 +157,15 @@
 
                All refer to past, can be repeated and will be accumulated.
 
-               Units  can  be  abbreviated  to  any length, with the otherwise
+               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,  hun-
-               dred.  Additionally,  the  unit  may  be  preceded by "last" or
+               Number  can also be written out one, two, ..., ten, dozen, hun-
+               dred. 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
+               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
@@ -220,9 +220,9 @@
 
 
SEE ALSO

 
-       notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1),  not-
-       much-hooks(5),  notmuch-new(1),  notmuch-reply(1),  notmuch-restore(1),
-       notmuch-search(1), notmuch-show(1), notmuch-tag(1)
+       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(1), notmuch-show(1), notmuch-tag(1)
 

 
-
Notmuch 0.15.2

+
Notmuch 0.16

diff --git a/manpages/notmuch-setup-1.mdwn b/manpages/notmuch-setup-1.mdwn
index 131258d..5359098 100644
--- a/manpages/notmuch-setup-1.mdwn
+++ b/manpages/notmuch-setup-1.mdwn
@@ -7,7 +7,7 @@
 
 
SYNOPSIS

 
-       notmuch command [args ...]
+       notmuch [option ...] command [arg ...]
 

 
 
DESCRIPTION

@@ -37,55 +37,73 @@
        the most widely used at this time.
+

OPTIONS

+
+       Supported global options for notmuch include
+
+           --help
+
+               Print a synopsis of available commands and exit.
+
+           --version
+
+               Print the installed version of notmuch, and exit.
+
+           --config=FILE
+
+               Specify the configuration file to use. This overrides any  con-
+               figuration file specified by ${NOTMUCH_CONFIG}.
+
+

COMMANDS

  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  and  count  commands  are  used  to query the email
-       database.
+       The search, show and count commands are used to query the  email  data-
+       base.
 
-       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 int the notmuch
+       The config command can be used to get or set settings int  the  notmuch
        configuration file.
@@ -95,16 +113,25 @@ 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- + 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 + stderr) Xapian queries it constructs.

SEE ALSO

        notmuch-config(1), notmuch-count(1), notmuch-dump(1), notmuch-hooks(5),
-       notmuch-new(1),    notmuch-reply(1),    notmuch-restore(1),    notmuch-
-       search(1), notmuch-search-terms(7), notmuch-show(1), notmuch-tag(1)
+       notmuch-insert(1),     notmuch-new(1),    notmuch-reply(1),    notmuch-
+       restore(1),   notmuch-search(1),   notmuch-search-terms(7),    notmuch-
+       show(1), notmuch-tag(1)
 
        The notmuch website: http://notmuchmail.org
@@ -119,4 +146,4 @@ (server: irc.freenode.net, channel: #notmuch). -

Notmuch 0.15.2

+

Notmuch 0.16

diff --git a/manpages/notmuch-show-1.mdwn b/manpages/notmuch-show-1.mdwn index ceac45c..00666bd 100644 --- a/manpages/notmuch-show-1.mdwn +++ b/manpages/notmuch-show-1.mdwn @@ -126,35 +126,40 @@ Decrypt any MIME encrypted parts found in the selected content (ie. "multipart/encrypted" parts). Status of the decryption will be reported (currently only supported with --format=json - and --format=sexp) and the multipart/encrypted part will be re- - placed by the decrypted content. Implies --verify. + and --format=sexp) and on successful decryption the multi- + part/encrypted part will be replaced by the decrypted content. + + Decryption expects a functioning gpg-agent(1) to provide any + needed credentials. Without one, the decryption will fail. + + Implies --verify. --exclude=(true|false) - Specify whether to omit threads only matching search.tag_ex- - clude from the search results (the default) or not. In either - case the excluded message will be marked with the exclude flag - (except when output=mbox when there is nowhere to put the + Specify whether to omit threads only matching search.tag_ex- + clude from the search results (the default) or not. In either + case the excluded message will be marked with the exclude flag + (except when output=mbox when there is nowhere to put the flag). - If --entire-thread is specified then complete threads are re- + If --entire-thread is specified then complete threads are re- turned regardless (with the excluded flag being set when appro- - priate) but threads that only match in an excluded message are + priate) but threads that only match in an excluded message are not returned when --exclude=true. The default is --exclude=true. --body=(true|false) - If true (the default) notmuch show includes the bodies of the - messages in the output; if false, bodies are omitted. - --body=false is only implemented for the json and sexp formats + If true (the default) notmuch show includes the bodies of the + messages in the output; if false, bodies are omitted. + --body=false is only implemented for the json and sexp formats and it is incompatible with --part >&gt; 0. - This is useful if the caller only needs the headers as body- + This is useful if the caller only needs the headers as body- less output is much faster and substantially smaller. - A common use of notmuch show is to display a single thread of email + A common use of notmuch show is to display a single thread of email messages. For this, use a search term of "thread:<thread-id>" as can be seen in the first column of output from the notmuch search command. @@ -170,9 +175,10 @@

SEE ALSO

-       notmuch(1),  notmuch-config(1), notmuch-count(1), notmuch-dump(1), not-
-       much-hooks(5),  notmuch-new(1),  notmuch-reply(1),  notmuch-restore(1),
-       notmuch-search(1), notmuch-search-terms(7), notmuch-tag(1)
+       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(1),  notmuch-search-terms(7),  not-
+       much-tag(1)
-

Notmuch 0.15.2

+

Notmuch 0.16

diff --git a/manpages/notmuch-tag-1.mdwn b/manpages/notmuch-tag-1.mdwn index cb0df55..29a1a89 100644 --- a/manpages/notmuch-tag-1.mdwn +++ b/manpages/notmuch-tag-1.mdwn @@ -8,7 +8,7 @@

SYNOPSIS

-       notmuch tag +<tag>|-<tag> [...] [--] <search-term> [...]
+       notmuch tag [options...] +<tag>|-<tag> [...] [--] <search-term> [...]
 
        notmuch tag --batch [ --input=<filename> ]
@@ -35,6 +35,14 @@ Supported options for tag include + --remove-all + + Remove all tags from each message matching the search terms + before applying the tag changes appearing on the command line. + This means setting the tags of each message to the tags to be + added. If there are no tags to be added, the messages will have + no tags. + --batch Read batch tagging operations from a file (stdin by default). @@ -95,8 +103,9 @@

SEE ALSO

        notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1),  not-
-       much-hooks(5),  notmuch-new(1),  notmuch-reply(1),  notmuch-restore(1),
-       notmuch-search(1), notmuch-search-terms(7), notmuch-show(1),
+       much-hooks(5),   notmuch-insert(1),  notmuch-new(1),  notmuch-reply(1),
+       notmuch-restore(1),  notmuch-search(1),  notmuch-search-terms(7),  not-
+       much-show(1),
-

Notmuch 0.15.2

+

Notmuch 0.16

diff --git a/news/release-0.16.mdwn b/news/release-0.16.mdwn new file mode 100644 index 0000000..8087161 --- /dev/null +++ b/news/release-0.16.mdwn @@ -0,0 +1,111 @@ +[[!meta date="2013-08-03"]] + +Notmuch 0.16 (2013-08-03) +========================= + +Command-Line Interface +---------------------- + +### Support for delivering messages to Maildir + +There is a new command `insert` that adds a message to a Maildir +folder and notmuch index. + +### `notmuch count --batch` option + +`notmuch count` now supports batch operations similar to `notmuch +tag`. This is mostly an optimization for remote notmuch usage. + +### `notmuch tag` option to remove all tags from matching messages + +`notmuch tag --remove-all` option has been added to remove all tags +from matching messages. This can be combined with adding new tags, +resulting in setting (rather than modifying) the tags of the +messages. + +### Decrypting commands explicitly expect a gpg-agent + +Decryption in `notmuch show` and `notmuch reply` has only ever +worked with a functioning gpg-agent. This is now made explicit in +code and documentation. The functional change is that it's now +possible to have gpg-agent running, but gpg "use-agent" +configuration option disabled, not forcing the user to use the agent +everywhere. + +### Configuration file saves follow symbolic links + +The notmuch commands that save the configuration file now follow +symbolic links instead of overwrite them. + +### Top level option to specify configuration file + +It's now possible to specify the configuration file to use on the +command line using the `notmuch --config=FILE` option. + +### Bash command-line completion + +The notmuch command-line completion support for the bash shell has +been rewritten. Supported completions include all the notmuch +commands, command-line arguments, values for keyword arguments, +search prefixes (such as "subject:" or "from:") in all commands that +use search terms, tags after + and - in `notmuch tag`, tags after +"tag:" prefix, user's email addresses after "from:" and "to:" +prefixes, and config options (and some config option values) in +`notmuch config`. The new completion support depends on the +bash-completion package. + +Deprecated commands "part" and "search-tags" are removed. + +Emacs Interface +--------------- + +### New keymap to view/save parts; removed s/v/o/| part button bindings + +The commands to view, save, and open MIME parts are now prefixed +with "." (". s" to save, ". v" to view, etc) and can be invoked with +point anywhere in a part, unlike the old commands, which were +restricted to part buttons. The old "s"/"v"/"o"/"|" commands on +part buttons have been removed since they clashed with other +bindings (notably "s" for search!) and could not be invoked when +there was no part button. The new, prefixed bindings appear in +show's help, so you no longer have to memorize them. + +### Default part save directory is now `mm-default-directory` + +Previously, notmuch offered to save parts and attachments to a mix +of `mm-default-directory`, `mailcap-download-directory`, and `~/`. +This has been standardized on `mm-default-directory`. + +### Key bindings for next/previous thread + +Show view has new key bindings M-n and M-p to move to the next and +previous thread in the search results. + +### Better handling of errors in search buffers + +Instead of interleaving errors in search result buffers, search mode +now reports errors in the minibuffer. + +### Faster search and show + +Communication between Emacs and the notmuch CLI is now more +efficient because it uses the CLI's S-expression support. As a +result, search mode should now fill search buffers faster and +threads should show faster. + +### No Emacs 22 support + +The Emacs 22 support added late 2010 was sufficient only for a short +period of time. After being incomplete for roughly 2 years the code +in question was now removed from this release. + +Vim Front-End +------------- + +The vim based front-end has been replaced with a new one that uses the Ruby +bindings. The old font-end is available in the contrib subfolder. + +Python Bindings +--------------- + +Fix loading of libnotmuch shared library on OS X (Darwin) systems.