Open pxsalehi opened 7 years ago
+1
This is the closest topic I could find on the subject. In org-mode all of the followings ranged events are showed in org-agenda as ranges:
test_1
SCHEDULED: <2019-10-07 Mo>--<2019-10-11 Fr>
test_2 <2019-10-07 Mo>--<2019-10-11 Fr>
test_3
<2019-10-07 Mo>--<2019-10-11 Fr>
In Orgzly, apparently agenda queries like ad.30
only understand format number 1 from the above list. Without user interface in Orgzly to adjust the date range.
With single-date timestamp being supported like <2019-10-11 Fr>
and <2019-10-11 Fr +1m>
one might expect the above ranged timestamps in format number 3 from the above list to be supported by Orgzly agenda queries like ad.30
in the same way? Should this be treated as bug? Is this ticker the right place to handle this?
Looks like a bug. You can open a new issue, as this one is for supporting ranges in UI.
Despite the parser and reminder/agenda features supporting range timestamps like
<2004-08-23 Mon>--<2004-08-26 Thu>
, when creating a new tasks it is not possible to give it a range timestamp.