<pre>
Supported global options for <b>notmuch</b> include
- <b>--help</b> Print a synopsis of available commands and exit.
+ <b>--help</b> <b>[command-name]</b>
+ Print a synopsis of available commands and exit. With an
+ optional command name, show the man page for that subcommand.
<b>--version</b>
Print the installed version of notmuch, and exit.
<b>--config=FILE</b>
Specify the configuration file to use. This overrides any
configuration file specified by ${NOTMUCH_CONFIG}.
+
+ <b>--uuid=HEX</b>
+ Enforce that the database UUID (a unique identifier which
+ persists until e.g. the database is compacted) is HEX; exit
+ with an error if it is not. This is useful to detect rollover
+ in modification counts on messages. You can find this UUID
+ using e.g. <b>notmuch</b> <b>count</b> <b>--lastmod</b>
+
+ All global options except <b>--config</b> can also be specified after the com‐
+ mand. For example, <b>notmuch</b> <b>subcommand</b> <b>--uuid=HEX</b> is equivalent to <b>not-</b>
+ <b>much</b> <b>--uuid=HEX</b> <b>subcommand</b>.
</pre>
<h2>COMMANDS</h2>
<h2>COPYRIGHT</h2>
<pre>
- 2015, Carl Worth and many others
+ 2009-2015, Carl Worth and many others
</pre>
-<h2>0.20.2</h2>
+<h2>0.21</h2>
Note: With this option, addresses are printed only after
the whole search is finished. This may take long time.
+ <b>--deduplicate=(no|mailbox|address)</b>
+ Control the deduplication of results.
+
+ <b>no</b> Output all occurences of addresses in the matching mes‐
+ sages. This is not applicable with --output=count.
+
+ <b>mailbox</b>
+ Deduplicate addresses based on the full, case sensitive
+ name and email address, or mailbox. This is effectively
+ the same as piping the --deduplicate=no output to <b>sort</b> <b>|</b>
+ <b>uniq</b>, except for the order of results. This is the
+ default.
+
+ <b>address</b>
+ Deduplicate addresses based on the case insensitive
+ address part of the mailbox. Of all the variants (with
+ different name or case), print the one occurring most
+ frequently among the matching messages. If --output=count
+ is specified, include all variants in the count.
+
<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
cal order, (that is, the newest results will be displayed
first).
- This option is not supported with --output=count.
+ However, if either --output=count or --deduplicate=address is
+ specified, this option is ignored and the order of the
+ results is unspecified.
<b>--exclude=(true|false)</b>
A message is called "excluded" if it matches at least one tag
<h2>COPYRIGHT</h2>
<pre>
- 2015, Carl Worth and many others
+ 2009-2015, Carl Worth and many others
</pre>
-<h2>0.20.2</h2>
+<h2>0.21</h2>
<h2>COPYRIGHT</h2>
<pre>
- 2015, Carl Worth and many others
+ 2009-2015, Carl Worth and many others
</pre>
-<h2>0.20.2</h2>
+<h2>0.21</h2>
<h2>COPYRIGHT</h2>
<pre>
- 2015, Carl Worth and many others
+ 2009-2015, Carl Worth and many others
</pre>
-<h2>0.20.2</h2>
+<h2>0.21</h2>
option is not compatible with specifying search terms on the
command line.
+ <b>--lastmod</b>
+ Append lastmod (counter for number of database updates) and
+ UUID to the output. lastmod values are only comparable
+ between databases with the same UUID.
+
<b>--input=<filename></b>
Read input from given file, instead of from stdin. Implies
<b>--batch</b>.
<h2>COPYRIGHT</h2>
<pre>
- 2015, Carl Worth and many others
+ 2009-2015, Carl Worth and many others
</pre>
-<h2>0.20.2</h2>
+<h2>0.21</h2>
<h2>COPYRIGHT</h2>
<pre>
- 2015, Carl Worth and many others
+ 2009-2015, Carl Worth and many others
</pre>
-<h2>0.20.2</h2>
+<h2>0.21</h2>
<h2>COPYRIGHT</h2>
<pre>
- 2015, Carl Worth and many others
+ 2009-2015, Carl Worth and many others
</pre>
-<h2>0.20.2</h2>
+<h2>0.21</h2>
<h2>COPYRIGHT</h2>
<pre>
- 2015, Carl Worth and many others
+ 2009-2015, Carl Worth and many others
</pre>
-<h2>0.20.2</h2>
+<h2>0.21</h2>
<h2>COPYRIGHT</h2>
<pre>
- 2015, Carl Worth and many others
+ 2009-2015, Carl Worth and many others
</pre>
-<h2>0.20.2</h2>
+<h2>0.21</h2>
<h2>COPYRIGHT</h2>
<pre>
- 2015, Carl Worth and many others
+ 2009-2015, Carl Worth and many others
</pre>
-<h2>0.20.2</h2>
+<h2>0.21</h2>
<h2>COPYRIGHT</h2>
<pre>
- 2015, Carl Worth and many others
+ 2009-2015, Carl Worth and many others
</pre>
-<h2>0.20.2</h2>
+<h2>0.21</h2>
<h2>COPYRIGHT</h2>
<pre>
- 2015, Carl Worth and many others
+ 2009-2015, Carl Worth and many others
</pre>
-<h2>0.20.2</h2>
+<h2>0.21</h2>
· date:<since>..<until>
+ · lastmod:<initial-revision>..<final-revision>
+
The <b>from:</b> prefix is used to match the name or address of the sender of
an email message.
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.
</pre>
<h3> Operators</h3>
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:<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. (Note that entering date:<expr> without "..", for example
+ date:yesterday, won't work, as it's not interpreted as a range expres‐
+ sion at all. Again, use date:yesterday..!)
+
+ 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.
ble 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..yesterday).
</pre>
<h3> Relative date and time</h3>
<h2>COPYRIGHT</h2>
<pre>
- 2015, Carl Worth and many others
+ 2009-2015, Carl Worth and many others
</pre>
-<h2>0.20.2</h2>
+<h2>0.21</h2>
<h2>COPYRIGHT</h2>
<pre>
- 2015, Carl Worth and many others
+ 2009-2015, Carl Worth and many others
</pre>
-<h2>0.20.2</h2>
+<h2>0.21</h2>
<h2>COPYRIGHT</h2>
<pre>
- 2015, Carl Worth and many others
+ 2009-2015, Carl Worth and many others
</pre>
-<h2>0.20.2</h2>
+<h2>0.21</h2>
projects / notmuch-wiki / commitdiff