X-Git-Url: https://git.notmuchmail.org/git?p=notmuch-wiki;a=blobdiff_plain;f=manpages%2Fnotmuch-search-terms-7.mdwn;h=a2e11ef46c04ed04a82778fe29f1022f6303ca57;hp=d6d3241965f5a8d391025863190beb6c3d0e50f7;hb=7ab49d222b1bafd16ce17aa2a8f21648fb3ac8fd;hpb=2db88ae8b0f1f2cdfeb8cdd701de15c38a74c605
diff --git a/manpages/notmuch-search-terms-7.mdwn b/manpages/notmuch-search-terms-7.mdwn
index d6d3241..a2e11ef 100644
--- a/manpages/notmuch-search-terms-7.mdwn
+++ b/manpages/notmuch-search-terms-7.mdwn
@@ -30,8 +30,8 @@
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.
Search prefixes
@@ -107,8 +107,8 @@
specified relative to the top-level maildir (and without the
leading slash). By default, path: 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. path:"" matches messages in the root of the mail
+ sages in the specified directory and all its subdirectories reâ
+ cursively. path:"" matches messages in the root of the mail
store and, likewise, path:** matches all messages.
path: will find a message if any copy of that message is in the
@@ -120,8 +120,8 @@
maildir, this includes messages in the "new" and "cur" subdirecâ
tories. The exact syntax for maildir folders depends on your
mail configuration. For maildir++, folder:"" 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 folder:.classes.topology. For "file system" maildir, the
inbox is typically folder:INBOX and nested folders are separated
by slashes, such as folder:classes/topology.
@@ -165,8 +165,8 @@
key can be present on a given message with several different
values. See notmuch-properties(7) for more details.
- User defined prefixes are also supported, see notmuch-config(1) for
- details.
+ User defined prefixes are also supported, see notmuch-config(1) for deâ
+ tails.
Operators
@@ -216,8 +216,8 @@
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.
@@ -229,10 +229,10 @@
Boolean and Probabilistic Prefixes
- Xapian (and hence notmuch) prefixes are either boolean, supporting
- exact matches like "tag:inbox" or probabilistic, supporting a more
- flexible term based searching. Certain special prefixes are processed
- by notmuch in a way not strictly fitting either of Xapian's built in
+ Xapian (and hence notmuch) prefixes are either boolean, supporting exâ
+ act matches like "tag:inbox" or probabilistic, supporting a more flexiâ
+ ble term based searching. Certain special 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.
Boolean
@@ -253,13 +253,13 @@
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 to:, from:, and subject:. In particular
@@ -325,8 +325,8 @@
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.
@@ -352,8 +352,8 @@
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
@@ -365,40 +365,40 @@
Supported absolute time formats
- · 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
Supported absolute date formats
- · 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.
@@ -409,9 +409,9 @@
Time zones
- · (+|-)HH:MM
+ ⢠(+|-)HH:MM
- · (+|-)HH[MM]
+ ⢠(+|-)HH[MM]
Some time zone codes, e.g. UTC, EET.
@@ -431,7 +431,7 @@
COPYRIGHT
- 2009-2020, Carl Worth and many others
+ 2009-2021, Carl Worth and many others
-0.31
+0.32