- <b>tags</b> Output all tags that appear on any message matching the
- search terms, either one per line (--format=text), sepa‐
- rated by null characters (--format=text0), as a JSON
- array (--format=json), or as an S-Expression list (--for‐
- mat=sexp).
-
- <b>--sort=(newest-first|oldest-first)</b>
- This option can be used to present results in either chrono‐
- logical order (<b>oldest-first</b>) or reverse chronological order
- (<b>newest-first</b>).
-
- Note: The thread order will be distinct between these two
- options (beyond being simply reversed). When sorting by <b>old-</b>
- <b>est-first</b> the threads will be sorted by the oldest message in
- each thread, but when sorting by <b>newest-first</b> the threads
- will be sorted by the newest message in each thread.
-
- By default, results will be displayed in reverse chronologi‐
- cal order, (that is, the newest results will be displayed
- first).
-
- <b>--offset=[-]N</b>
- Skip displaying the first N results. With the leading '-',
- start at the Nth result from the end.
-
- <b>--limit=N</b>
- Limit the number of displayed results to N.
-
- <b>--exclude=(true|false|all|flag)</b>
- 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, <b>true</b>, prevents excluded messages from
- matching the search terms.
-
- <b>all</b> additionally prevents excluded messages from appearing in
- displayed results, in effect behaving as though the excluded
- messages do not exist.
-
- <b>false</b> allows excluded messages to match search terms and
- appear in displayed results. Excluded messages are still
- marked in the relevant outputs.
-
- <b>flag</b> only has an effect when <b>--output=summary</b>. The output is
- almost identical to <b>false</b>, but the "match count" is the num‐
- ber of matching non-excluded messages in the thread, rather
- than the number of matching messages.
-
- <b>--duplicate=N</b>
- For <b>--output=files</b>, output the Nth filename associated with
- each message matching the query (N is 1-based). If N is
- greater than the number of files associated with the message,
- don't print anything.
-
- For <b>--output=messages</b>, only output message IDs of messages
- matching the search terms that have at least N filenames
- associated with them.
-
- Note that this option is orthogonal with the <b>folder:</b> search
- prefix. The prefix matches messages based on filenames. This
- option filters filenames of the matching messages.
+ <b>tags</b> Output all tags that appear on any message matching the
+ search terms, either one per line (<b>--format=text</b>), sepa‐
+ rated by null characters (<b>--format=text0</b>), as a JSON ar‐
+ ray (<b>--format=json</b>), or as an S-Expression list (<b>--for-</b>
+ <b>mat=sexp</b>).
+
+ <b>--sort=(newest-first|oldest-first)</b>
+ This option can be used to present results in either chronologi‐
+ cal order (<b>oldest-first</b>) or reverse chronological order (<b>new-</b>
+ <b>est-first</b>).
+
+ Note: The thread order will be distinct between these two op‐
+ tions (beyond being simply reversed). When sorting by <b>old-</b>
+ <b>est-first</b> the threads will be sorted by the oldest message in
+ each thread, but when sorting by <b>newest-first</b> the threads will
+ be sorted by the newest message in each thread.
+
+ By default, results will be displayed in reverse chronological
+ order, (that is, the newest results will be displayed first).
+
+ <b>--offset=[-]N</b>
+ Skip displaying the first N results. With the leading '-', start
+ at the Nth result from the end.
+
+ <b>--limit=N</b>
+ Limit the number of displayed results to N.
+
+ <b>--exclude=(true|false|all|flag)</b>
+ A message is called "excluded" if it matches at least one tag in
+ search.exclude_tags that does not appear explicitly in the
+ search terms. This option specifies whether to omit excluded
+ messages in the search process.
+
+ <b>true</b> <b>(default)</b>
+ Prevent excluded messages from matching the search terms.
+
+ <b>all</b> Additionally prevent excluded messages from appearing in
+ displayed results, in effect behaving as though the ex‐
+ cluded messages do not exist.
+
+ <b>false</b> Allow excluded messages to match search terms and appear
+ in displayed results. Excluded messages are still marked
+ in the relevant outputs.
+
+ <b>flag</b> Only has an effect when <b>--output=summary</b>. The output is
+ almost identical to <b>false</b>, but the "match count" is the
+ number of matching non-excluded messages in the thread,
+ rather than the number of matching messages.
+
+ <b>--duplicate=N</b>
+ For <b>--output=files</b>, output the Nth filename associated with each
+ message matching the query (N is 1-based). If N is greater than
+ the number of files associated with the message, don't print
+ anything.
+
+ For <b>--output=messages</b>, only output message IDs of messages
+ matching the search terms that have at least N filenames associ‐
+ ated with them.
+
+ Note that this option is orthogonal with the <b>folder:</b> search pre‐
+ fix. The prefix matches messages based on filenames. This option
+ filters filenames of the matching messages.
+</pre>
+
+<h2>EXAMPLE</h2>
+<pre>
+ The following shows an example of the summary output format, with one
+ message having multiple filenames.
+
+ % notmuch search date:today.. and tag:bad-news
+ thread:0000000000063c10 Today [1/1] Some Persun; To the bone (bad-news inbox unread)
+ thread:0000000000063c25 Today [1/1(2)] Ann Other; Bears (bad-news inbox unread)
+ thread:0000000000063c00 Today [1/1] A Thurd; Bites, stings, sad feelings (bad-news unread)