X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=manpages%2Fnotmuch-search-terms-7.mdwn;h=634fde4f647c431c04feac5c10e058ead0d61743;hb=df77a5ccd1b0581b1cb3a7ebcf14df7eb048053b;hp=985548d75173d4dbbaf4ee3bfa85539ee53ebc34;hpb=dee880643fd8d50e6c67bda0b8a43d37545efb5b;p=obsolete%2Fnotmuch-wiki diff --git a/manpages/notmuch-search-terms-7.mdwn b/manpages/notmuch-search-terms-7.mdwn index 985548d..634fde4 100644 --- a/manpages/notmuch-search-terms-7.mdwn +++ b/manpages/notmuch-search-terms-7.mdwn @@ -1,4 +1,4 @@ -
@@ -96,59 +96,59 @@ <initial-timestamp>..<final-timestamp> - Each timestamp is a number representing the number of seconds since + Each timestamp is a number representing the number of seconds since 1970-01-01 00:00:00 UTC. - In addition to individual terms, multiple terms can be combined with - Boolean operators ( and, or, not , etc.). Each term in the query will - be implicitly connected by a logical AND if no explicit operator is - provided, (except that terms with a common prefix will be implicitly + In addition to individual terms, multiple terms can be combined with + Boolean operators ( and, or, not , etc.). Each term in the query will + be implicitly connected by a logical AND if no explicit operator is + provided, (except that terms with a common prefix will be implicitly combined with OR until we get Xapian defect #402 fixed). - Parentheses can also be used to control the combination of the Boolean - operators, but will have to be protected from interpretation by the - shell, (such as by putting quotation marks around any parenthesized + Parentheses can also be used to control the combination of the Boolean + operators, but will have to be protected from interpretation by the + shell, (such as by putting quotation marks around any parenthesized expression).
- notmuch understands a variety of standard and natural ways of express- + 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 + 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 the syntax supported for absolute and relative terms is given below. The range expression date:<since>..<until> - The above expression restricts the results to only messages + The above expression restricts the results to only messages from <since> to <until>, based on the Date: header. <since> and <until> can describe imprecise times, such as "yes- - terday". 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 yester- + terday". 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 yester- day). Similarly, date:january..february matches from the begin- ning of January to the end of February. - Currently, we do not support spaces in range expressions. You + 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 + some cases) 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 - possible 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 + possible 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..yester- + 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..yester- day). Relative date and time @@ -157,15 +157,15 @@ All refer to past, can be repeated and will be accumulated. - Units can be abbreviated to any length, with the otherwise + 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, hun- - dred. Additionally, the unit may be preceded by "last" or + Number can also be written out one, two, ..., ten, dozen, hun- + dred. Additionally, 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 specification will be relative from the specified + When combined with absolute date and time, the relative date + and time specification will be relative from the specified absolute date and time. Examples: 5M2d, two weeks @@ -220,7 +220,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-new(1), notmuch-reply(1), notmuch-restore(1), notmuch-search(1), notmuch-show(1), notmuch-tag(1)