mirror of
https://git.notmuchmail.org/git/notmuch
synced 2024-12-22 17:34:54 +01:00
TODO: update entry on date range queries
This commit is contained in:
parent
b12b81bbb5
commit
aa48b23f38
1 changed files with 7 additions and 6 deletions
13
devel/TODO
13
devel/TODO
|
@ -146,12 +146,13 @@ vs. tag-when-all-files-flagged (* above)).
|
||||||
Add an interface to accept a "key" and a byte stream, rather than a
|
Add an interface to accept a "key" and a byte stream, rather than a
|
||||||
filename.
|
filename.
|
||||||
|
|
||||||
Provide a sane syntax for date ranges. First, we don't want to require
|
Improve syntax for date ranges queries. date:expr should be
|
||||||
both endpoints to be specified. For example it would be nice to be
|
interpreted as date:expr..expr so that, for example, "date:2013-01-22"
|
||||||
able to say things like "since:2009-01-1" or "until:2009-01-1" and
|
would cover the whole of the specified day (currently that's not even
|
||||||
have the other endpoint be implicit. Second we'd like to support
|
recognized as a date range expression). It might be nice to be able to
|
||||||
relative specifications of time such as "since:'2 months ago'". To do
|
use things like "since:2013-01-22" and "until:2013-01-22" as synonyms
|
||||||
any of this we're probably going to need to break down an write our
|
to "date:2013-01-22.." and "date:..2013-01-22", respectively. To do
|
||||||
|
any of this we're probably going to need to break down and write our
|
||||||
own parser for the query string rather than using Xapian's QueryParser
|
own parser for the query string rather than using Xapian's QueryParser
|
||||||
class.
|
class.
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue