I’m happy to announce release of telltime 0.0.1, a small cli tool for interacting with Daypack-lib (a schedule, time, time slots handling library) components.
It primarily answers time related queries, with support for union (||), intersect (&&) and “ordered select” (>>, explanation of this is at the bottom).
The query language, time expression, aims to mimic natural language, but without ambiguity. The grammar is only documented in the online demo here at the moment.
Some examples copied from the README are as follows.
Search for time slots matching Daypack time expression
“Hm, I wonder what years have Febuary 29th?”
$ telltime search --time-slots 5 --years 100 "feb 29 00:00"
Searching in time zone offset (seconds) : 36000
Search by default starts from (in above time zone) : 2020 Sep 03 19:24:15
Matching time slots (in above time zone):
[2024 Feb 29 00:00:00, 2024 Feb 29 00:00:01)
[2028 Feb 29 00:00:00, 2028 Feb 29 00:00:01)
[2032 Feb 29 00:00:00, 2032 Feb 29 00:00:01)
[2036 Feb 29 00:00:00, 2036 Feb 29 00:00:01)
[2040 Feb 29 00:00:00, 2040 Feb 29 00:00:01)
“Would be handy to know what this cron expression refers to”
$ telltime search --time-slots 5 "0 4 8-14 * *"
Searching in time zone offset (seconds) : 36000
Search by default starts from (in above time zone) : 2020 Sep 06 17:39:56
Matching time slots (in above time zone):
[2020 Sep 08 04:00:00, 2020 Sep 08 04:01:00)
[2020 Sep 09 04:00:00, 2020 Sep 09 04:01:00)
[2020 Sep 10 04:00:00, 2020 Sep 10 04:01:00)
[2020 Sep 11 04:00:00, 2020 Sep 11 04:01:00)
[2020 Sep 12 04:00:00, 2020 Sep 12 04:01:00)
“I have a bunch of time ranges, but some of them overlap, and they are not in the right order. If only there is a way to combine and sort them easily.”
$ telltime search --time-slots 1000 "2020 . jan . 1, 10, 20 . 13:00 to 14:00 \
|| 2019 dec 25 13:00 \
|| 2019 dec 25 10am to 17:00 \
|| 2020 jan 5 10am to 1:30pm \
|| 2020 . jan . 7 to 12 . 9:15am to 2:45pm"
Searching in time zone offset (seconds) : 36000
Search by default starts from (in above time zone) : 2020 Sep 06 18:01:12
Matching time slots (in above time zone):
[2019 Dec 25 10:00:00, 2019 Dec 25 17:00:00)
[2020 Jan 01 13:00:00, 2020 Jan 01 14:00:00)
[2020 Jan 05 10:00:00, 2020 Jan 05 13:30:00)
[2020 Jan 07 09:15:00, 2020 Jan 07 14:45:00)
[2020 Jan 08 09:15:00, 2020 Jan 08 14:45:00)
[2020 Jan 09 09:15:00, 2020 Jan 09 14:45:00)
[2020 Jan 10 09:15:00, 2020 Jan 10 14:45:00)
[2020 Jan 11 09:15:00, 2020 Jan 11 14:45:00)
[2020 Jan 12 09:15:00, 2020 Jan 12 14:45:00)
[2020 Jan 20 13:00:00, 2020 Jan 20 14:00:00)
Get exact time after some duration from now
$ telltime from-now "1 hour"
Now : 2020-09-03 15:53:29
Duration (original) : 1 hour
Duration (normalized) : 1 hours 0 mins 0 secs
Now + duration : 2020-09-03 16:53:29
$ telltime from-now "1.5 days 2.7 hours 0.5 minutes"
Now : 2020-09-03 15:55:43
Duration (original) : 1.5 days 2.7 hours 0.5 minutes
Duration (normalized) : 1 days 14 hours 42 mins 30 secs
Now + duration : 2020-09-05 06:38:13
Difference between ordered select and union
s1 >> s2 is similar to s1 || s2, but >> picks between s1 and s2 in a round robin fashion, instead of just picking the smallest between two.
One specific differing case would be when the search starts at 4pm today, 3pm || 5pm would return 5pm today and 3pm tomorrow, and so on, while 3pm >> 5pm would return 3pm tomorrow and 5pm tomorrow (a 5pm is only picked after a 3pm has been picked already).