Open memeplex opened 5 years ago
I understand it might be difficult to exclude past events by marking them DONE but I think this was recently solved in the same way org mode does it, wasn't it?
Org mode deals with this in the following way: when you try to mark such an entry DONE, using C-c C-t, it shifts the base date of the repeating timestamp by the repeater interval, and immediately sets the entry state back to TODO.
Ahhh ok, now I realize orgzly still matches the base date of a repeating timestamp! Coupled with the fact that marking a repeating task done advances the base date, this is indeed all I need to implement my use case. This lowers the priority of the request for me down to epsilon. Close it if you want.
I guess my request fits here:
Rationale: i have tasks that repeat daily, and tasks that repeat less often. I do not want to see daily tasks in my Agenda view, but in a seperate search instead. Currently i have to add a :daily:
tag manually to make this happen, which is error prone. Would be great to filter repeating intervals <= 1 day automatically :)
@nevenz , I'd add a case for interval timestamps as <2021-12-28>--<2021-12-31>
. I would help me in many cases a lot!
I think this is the right thing to do because:
IMO scheduling a repeating timestamp should be equivalent to adding a sequence of infinite periodically separated timestamps.
org mode does it and it doesn't seem to be any rationale for orgzly deviation here.
It allows to build agenda views including not only next actions but actions specifically scheduled for the day (with a repeating schedule or not, that shouldn't be a matter).
Currently, the only way to match repeating schedules is using the
ad
operator but this automatically adds day grouping which is nice for calendar style views but undesirable for next-actions style views.