diff options
| author | Lars Henriksen <LarsHenriksen@get2net.dk> | 2018-11-15 20:05:08 +0100 |
|---|---|---|
| committer | Lukas Fleischer <lfleischer@calcurse.org> | 2019-01-07 16:57:51 +0100 |
| commit | 4ba2cc46d74a3b516046d1da565e4abb4dc1b196 (patch) | |
| tree | a4398251db85d6dfefdeb642765a7fcd0e792469 /%2525253fid%2525253dd0602625bcb0af0ec37b74597630c156b188afef%25253fid%25253ddaa30ef3bb592cea54dbdbce0f241bab43eec5dc%253fid%253dad183c61a93ca0146407d314d4ae671c894f88a8%3fid%3d7851f46fbb1e84fe4fa62a36d1f79b936f040e66?id=4ba2cc46d74a3b516046d1da565e4abb4dc1b196 | |
| parent | 42e296c8403e52e46abb5fea70b65ae40a0425f3 (diff) | |
CLI: time assignments for filter options
Explanation. There is an important difference between "to <date>" (e.g.
to 15/11/2018) and "to <date time>" (e.g. to "15/11/2018 13:30"):
<date> is a time span (of 24 hours), while <date time> is a point in
time.
"To <date>" really means "to the end of <date>", while "before <date>"
means "before the beginning of <date>". There are 24 hours between the
two, whereas there is only one second between "before <date time>" and
"to <date time>". Similar for from/after.
An earlier commit introduced parse_datearg() that only accepts a date
without a time. Hence, a date should be treated as a time span from
midnight to one second before next midnight.
The commit also fixes an error detection bug (filter.start_from/to and
filter.end_from/to were updated too early).
Signed-off-by: Lukas Fleischer <lfleischer@calcurse.org>
Diffstat (limited to '%2525253fid%2525253dd0602625bcb0af0ec37b74597630c156b188afef%25253fid%25253ddaa30ef3bb592cea54dbdbce0f241bab43eec5dc%253fid%253dad183c61a93ca0146407d314d4ae671c894f88a8%3fid%3d7851f46fbb1e84fe4fa62a36d1f79b936f040e66?id=4ba2cc46d74a3b516046d1da565e4abb4dc1b196')
0 files changed, 0 insertions, 0 deletions