Hi,
TL;DR
for the search subcommand, the semantic of positional argument end seems to be counterintuitive or not well documented. At least when day granularity is used.
Specifiying 20250630 as end does not show events on that day.
To make them appear user should specify 202506302359.
Current documentation just says
positional arguments:
text
start
end
with no other comment. Can this be improved?
Another option could be completing the end parameter with 2359 if user does not specify time.
version
Details
I issued a command like this:
gcalcli --calendar 'calendarname' search '*' 20250601 20250630 --tsv
in the output is like
....
2025-06-26 14:30 2025-06-26 17:30 Event1
2025-06-27 09:00 2025-06-27 11:00 Event2
2025-06-27 11:00 2025-06-27 13:00 Event3
2025-06-27 14:30 2025-06-27 17:30 Event4
But it does not show events on 2025-06-30.
They are shown if the command is
gcalcli --calendar 'calendarname' search '*' 20250601 20250701 --tsv
or
gcalcli --calendar 'calendarname' search '*' 20250601 202506302359 --tsv
Hi,
TL;DR
for the
searchsubcommand, the semantic of positional argumentendseems to be counterintuitive or not well documented. At least when day granularity is used.Specifiying
20250630as end does not show events on that day.To make them appear user should specify
202506302359.Current documentation just says
with no other comment. Can this be improved?
Another option could be completing the end parameter with
2359if user does not specify time.version
Details
I issued a command like this:
gcalcli --calendar 'calendarname' search '*' 20250601 20250630 --tsv
in the output is like
....
2025-06-26 14:30 2025-06-26 17:30 Event1
2025-06-27 09:00 2025-06-27 11:00 Event2
2025-06-27 11:00 2025-06-27 13:00 Event3
2025-06-27 14:30 2025-06-27 17:30 Event4
But it does not show events on 2025-06-30.
They are shown if the command is
or