X-Git-Url: https://git.cworth.org/git?p=notmuch-wiki;a=blobdiff_plain;f=manpages%2Fnotmuch-search-terms-7.mdwn;h=63d9fd8c0c8f3794636b91e55dcad7211b992c8f;hp=e46c6b5e9d024f942e882bb74d8b954da719a911;hb=0568dc66970180cbda48af10d27c49fb1a36805e;hpb=d755c1556a62870e6a065dcff4b91ded525b0e64 diff --git a/manpages/notmuch-search-terms-7.mdwn b/manpages/notmuch-search-terms-7.mdwn index e46c6b5..63d9fd8 100644 --- a/manpages/notmuch-search-terms-7.mdwn +++ b/manpages/notmuch-search-terms-7.mdwn @@ -40,9 +40,8 @@ terms to match against specific portions of an email, (where <brackets> indicate user-supplied values). - If notmuch is built with Xapian Field Processors (see below) some of - the prefixes with <regex> forms can be also used to restrict the - results to those whose value matches a regular expression (see + Some of the prefixes with <regex> forms can be also used to restrict + the results to those whose value matches a regular expression (see regex(7)) delimited with //, for example: notmuch search 'from:"/bob@.*[.]example[.]com/"' @@ -51,47 +50,46 @@ Match terms in the body of messages. from:<name-or-address> or from:/<regex>/ - The from: prefix is used to match the name or address of the + The from: prefix is used to match the name or address of the sender of an email message. to:<name-or-address> - The to: prefix is used to match the names or addresses of any + The to: prefix is used to match the names or addresses of any recipient of an email message, (whether To, Cc, or Bcc). subject:<word-or-quoted-phrase> or subject:/<regex>/ - Any term prefixed with subject: will match only text from the - subject of an email. Searching for a phrase in the subject is - supported by including quotation marks around the phrase, imme‐ + Any term prefixed with subject: will match only text from the + subject of an email. Searching for a phrase in the subject is + supported by including quotation marks around the phrase, imme‐ diately following subject:. attachment:<word> - The attachment: prefix can be used to search for specific file‐ + The attachment: prefix can be used to search for specific file‐ names (or extensions) of attachments to email messages. mimetype:<word> - The mimetype: prefix will be used to match text from the con‐ - tent-types of MIME parts within email messages (as specified by + The mimetype: prefix will be used to match text from the con‐ + tent-types of MIME parts within email messages (as specified by the sender). tag:<tag> or tag:/<regex>/ or is:<tag> or is:/<regex>/ - For tag: and is: valid tag values include inbox and unread by - default for new messages added by notmuch new as well as any + For tag: and is: valid tag values include inbox and unread by + default for new messages added by notmuch new as well as any other tag values added manually with notmuch tag. id:<message-id> or mid:<message-id> or mid:/<regex>/ - For id: and mid:, message ID values are the literal contents of - the Message-ID: header of email messages, but without the '<', + For id: and mid:, message ID values are the literal contents of + the Message-ID: header of email messages, but without the '<', '>' delimiters. thread:<thread-id> - The thread: prefix can be used with the thread ID values that - are generated internally by notmuch (and do not appear in email - messages). These thread ID values can be seen in the first col‐ + The thread: prefix can be used with the thread ID values that + are generated internally by notmuch (and do not appear in email + messages). These thread ID values can be seen in the first col‐ umn of output from notmuch search thread:{<notmuch query>} - If notmuch is built with Xapian Field Processors (see below), - threads may be searched for indirectly by providing an arbitrary + Threads may be searched for indirectly by providing an arbitrary notmuch query in {}. For example, the following returns threads containing a message from mallory and one (not necessarily the same message) with Subject containing the word "crypto". @@ -158,9 +156,7 @@ query:<name> The query: prefix allows queries to refer to previously saved - queries added with notmuch-config(1). Named queries are only - available if notmuch is built with Xapian Field Processors (see - below). + queries added with notmuch-config(1). property:<key>=<value> The property: prefix searches for messages with a particular @@ -329,22 +325,21 @@ since 1970-01-01 00:00:00 UTC. For example: date:@<initial-timestamp>..@<final-timestamp> - 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. With Xapian Field Processor support (see below), non-range - date queries such as date:yesterday will work, but otherwise will give - unexpected results; if in doubt use date:yesterday..! - - Currently, we do not support spaces in range expressions. You can + Currently, spaces in range expressions are not supported. 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 + 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‐ - 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. + Open-ended ranges are supported. I.e. it's possible to specify + date:..<until> or date:<since>.. to not limit the start or end time, + respectively. + + +

  Single expression

+
+       date:<expr> works as a shorthand for date:<expr>..<expr>.  For example,
+       date:monday matches from the beginning of Monday until the end of  Mon‐
+       day.

  Relative date and time

@@ -421,31 +416,11 @@ Some time zone codes, e.g. UTC, EET. -

XAPIAN FIELD PROCESSORS

-
-       Certain  optional  features  of the notmuch query processor rely on the
-       presence of the Xapian field processor API. You can determine  if  your
-       notmuch  was  built  against a sufficiently recent version of Xapian by
-       running
-
-          % notmuch config get built_with.field_processor
-
-       Currently the following features require field processor support:
-
-       · non-range date queries, e.g. "date:today"
-
-       · named queries e.g. "query:my_special_query"
-
-       · regular expression searches, e.g. "subject:/^\[SPAM\]/"
-
-       · thread subqueries, e.g. "thread:{from:bob}"
-
-

SEE ALSO

-       notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1),  not‐
-       much-hooks(5),  notmuch-insert(1),  notmuch-new(1), notmuch-reindex(1),
-       notmuch-properties(1),  *notmuch-reply(1),   notmuch-restore(1),   not‐
+       notmuch(1),  notmuch-config(1), notmuch-count(1), notmuch-dump(1), not‐
+       much-hooks(5), notmuch-insert(1),  notmuch-new(1),  notmuch-reindex(1),
+       notmuch-properties(1),   *notmuch-reply(1),   notmuch-restore(1),  not‐
        much-search(1), *notmuch-show(1), notmuch-tag(1)
@@ -456,7 +431,7 @@

COPYRIGHT

-       2009-2019, Carl Worth and many others
+       2009-2020, Carl Worth and many others
-

0.29

+

0.30