X-Git-Url: https://git.cworth.org/git?p=notmuch-wiki;a=blobdiff_plain;f=manpages%2Fnotmuch-search-terms-7.mdwn;h=61539a68dacf11fdfbd7121682153ee0cf0acdb5;hp=98e15c70038533c38e75a9e4db052adc550ff642;hb=6562766d20047abcb3bab0d88a1e5849baaae76d;hpb=8b6746d22f18e39db67f878267cc8415eef9559a
diff --git a/manpages/notmuch-search-terms-7.mdwn b/manpages/notmuch-search-terms-7.mdwn
index 98e15c7..61539a6 100644
--- a/manpages/notmuch-search-terms-7.mdwn
+++ b/manpages/notmuch-search-terms-7.mdwn
@@ -25,7 +25,7 @@
The search terms can consist of free-form text (and quoted phrases)
which will match all messages that contain all of the given
- terms/phrases in the body, the subject, or any of the sender or recipi-
+ 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
@@ -76,13 +76,13 @@
For id:, message ID values are the literal contents of the Message-ID:
header of email messages, but without the '<', '>' delimiters.
- The thread: prefix can be used with the thread ID values that are gen-
+ The thread: prefix can be used with the thread ID values that are genâ
erated internally by notmuch (and do not appear in email messages).
These thread ID values can be seen in the first column of output from
notmuch search
The path: prefix searches for email messages that are in particular
- directories within the mail store. The directory must be specified rel-
+ directories within the mail store. The directory must be specified relâ
ative to the top-level maildir (and without the leading slash). By
default, path: matches messages in the specified directory only. The
"/**" suffix can be used to match messages in the specified directory
@@ -90,19 +90,19 @@
the root of the mail store and, likewise, path:** matches all messages.
The folder: prefix searches for email messages by maildir or MH folder.
- For MH-style folders, this is equivalent to path:. For maildir, this
- includes messages in the "new" and "cur" subdirectories. The exact syn-
- tax 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 fold-
- ers are separated by "."s, such as folder:.classes.topology. For "file
+ For MH-style folders, this is equivalent to path:. For maildir, this
+ includes messages in the "new" and "cur" subdirectories. The exact synâ
+ tax 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 foldâ
+ ers 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.
- Both path: and folder: will find a message if any copy of that message
+ Both path: and folder: will find a message if any copy of that message
is in the specific directory/folder.
- The date: prefix can be used to restrict the results to only messages
+ The date: prefix can be used to restrict the results to only messages
within a particular time range (based on the Date: header) with a range
syntax of:
@@ -132,8 +132,8 @@
DATE AND TIME SEARCH
- 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-
+ 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
@@ -150,7 +150,7 @@
<since> and <until> can describe imprecise times, such as "yesterday".
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 yesterday). Similarly, date:january..febru-
+ 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
@@ -158,7 +158,7 @@
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 possi-
+ Open-ended ranges are supported (since Xapian 1.2.1), i.e. it's possiâ
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.
@@ -171,7 +171,7 @@
Relative date and time
- [N|number] (years|months|weeks|days|hours|hrs|minutes|mins|sec-
+ [N|number] (years|months|weeks|days|hours|hrs|minutes|mins|secâ
onds|secs) [...]
All refer to past, can be repeated and will be accumulated.
@@ -245,7 +245,7 @@
SEE ALSO
- notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1), not-
+ 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)
@@ -260,4 +260,4 @@
2014, Carl Worth and many others
-0.18
+0.18.1