mirror of
https://git.notmuchmail.org/git/notmuch
synced 2024-11-24 20:08:10 +01:00
Clarify the syntax required when searching using timestamps.
Need to be clearer about specifying time ranges using timestamps. Legacy syntax which predates the date prefix is still supported, but timestamps used in conjunction with the date prefix require additional syntax.
This commit is contained in:
parent
a9f1c7c294
commit
0cbe982bfd
1 changed files with 11 additions and 3 deletions
|
@ -121,13 +121,14 @@ date:<since>..<until> or date:<date>
|
||||||
expression, and supported syntax for <since> and <until> date and
|
expression, and supported syntax for <since> and <until> date and
|
||||||
time expressions.
|
time expressions.
|
||||||
|
|
||||||
The time range can also be specified using timestamps with a
|
The time range can also be specified using timestamps without
|
||||||
syntax of:
|
including the date prefix using a syntax of:
|
||||||
|
|
||||||
<initial-timestamp>..<final-timestamp>
|
<initial-timestamp>..<final-timestamp>
|
||||||
|
|
||||||
Each timestamp is a number representing the number of seconds
|
Each timestamp is a number representing the number of seconds
|
||||||
since 1970-01-01 00:00:00 UTC.
|
since 1970-01-01 00:00:00 UTC. Specifying a time range this way
|
||||||
|
is considered legacy and predates the date prefix.
|
||||||
|
|
||||||
lastmod:<initial-revision>..<final-revision>
|
lastmod:<initial-revision>..<final-revision>
|
||||||
The **lastmod:** prefix can be used to restrict the result by the
|
The **lastmod:** prefix can be used to restrict the result by the
|
||||||
|
@ -296,6 +297,13 @@ In this case, <since> is taken as the earliest time it could describe
|
||||||
could describe (the end of yesterday). Similarly, date:january..february
|
could describe (the end of yesterday). Similarly, date:january..february
|
||||||
matches from the beginning of January to the end of February.
|
matches from the beginning of January to the end of February.
|
||||||
|
|
||||||
|
If specifying a time range using timestamps in conjunction with the
|
||||||
|
date prefix, each timestamp must be preceded by @ (ASCII hex 40). As
|
||||||
|
above, each timestamp is a number representing the number of seconds
|
||||||
|
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
|
date:<expr>..! can be used as a shorthand for date:<expr>..<expr>. The
|
||||||
expansion takes place before interpretation, and thus, for example,
|
expansion takes place before interpretation, and thus, for example,
|
||||||
date:monday..! matches from the beginning of Monday until the end of
|
date:monday..! matches from the beginning of Monday until the end of
|
||||||
|
|
Loading…
Reference in a new issue