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> Search prefixes</h3>
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 "/**" suffix can be used to match mes‐
- sages in the specified directory and all its subdirectories
- recursively. <b>path:""</b> matches messages in the root of the mail
+ sages in the specified directory and all its subdirectories re‐
+ cursively. <b>path:""</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
maildir, this includes messages in the "new" and "cur" subdirec‐
tories. The exact syntax for maildir folders depends on your
mail configuration. For maildir++, <b>folder:""</b> matches the inbox
- folder (which is the root in maildir++), other folder names
- always start with ".", and nested folders are separated by "."s,
+ folder (which is the root in maildir++), other folder names al‐
+ ways start with ".", and nested folders are separated by "."s,
such as <b>folder:.classes.topology</b>. For "file system" maildir, the
inbox is typically <b>folder:INBOX</b> and nested folders are separated
by slashes, such as <b>folder:classes/topology</b>.
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> Operators</h3>
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.
+ get results for "Johnson"; 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>
<h3> Boolean and Probabilistic Prefixes</h3>
<pre>
- Xapian (and hence notmuch) prefixes are either <b>boolean</b>, supporting
- exact matches like "<u>tag:inbox</u>" 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's built in
+ Xapian (and hence notmuch) prefixes are either <b>boolean</b>, supporting ex‐
+ act matches like "<u>tag:inbox</u>" 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's built in
styles. The prefixes currently supported by notmuch are as follows.
<b>Boolean</b>
occur in that order. One useful, but initially surprising feature is
that the following are equivalent ways to write the same phrase.
- · "a list of words"
+ • "a list of words"
- · 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
since 1970-01-01 00:00:00 UTC. For example:
date:@<initial-timestamp>..@<final-timestamp>
- Currently, spaces in range expressions are not supported. You can
- replace the spaces with '_', or (in most cases) '-', or (in some cases)
+ Currently, spaces in range expressions are not supported. You can re‐
+ place 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.
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 "last" or "this" (e.g., "last
+ Number can also be written out one, two, ..., ten, dozen, hundred. Ad‐
+ ditionally, 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
<h3> 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> 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.
<h3> Time zones</h3>
<pre>
- · (+|-)HH:MM
+ • (+|-)HH:MM
- · (+|-)HH[MM]
+ • (+|-)HH[MM]
Some time zone codes, e.g. UTC, EET.
</pre>
<h2>COPYRIGHT</h2>
<pre>
- 2009-2020, Carl Worth and many others
+ 2009-2021, Carl Worth and many others
</pre>
-<h2>0.31</h2>
+<h2>0.32</h2>
projects / notmuch-wiki / blobdiff