I have a TODO in my recur.org file that looks like this:
** TODO Do this thing every day.
SCHEDULED: <2016-09-19 Mon .+1d>
For me it. up to + 1d means "if you happen to do this work late, then when you mark it as completed, it reschedules itself the day after it is marked as done." This is correct, because this task has a property which, if I do not do it within 4 days, then I do not need to do this 4 times to catch up, I just need to do it once. On the other hand, if I do not do this for 4 days, I really need to do this work, and I hope that it will be highlighted in red when I look at my weekly view on the agenda using C-c a aemacs org-mode.
Unfortunately, this does not happen. In the standard agenda view, this task is called
[stuff in red here with Sched. 4x etc etc]
recur: Scheduled: TODO [
and the record is in green without indicating that I'm late. This, apparently, because the fact that it is planned every day means, in particular, that it is appointed today, and therefore the fact that it is also planned 4 days ago hangs.
This is not the behavior I want. I would like to be able to make a repeated TODO, which, when done, resets the scheduled time to date + [interval], and yet I am still warned if I do not complete the task for a period of time that exceeds the interval.
Experiments show that working with such things as .+1wbehaves the same way - they are 6 days past due, and then suddenly they are no longer past due.
Can I write a custom agenda command to ensure that these tasks are marked when they are late?
3 : , - TODO, , .
, - . C-c a L , , , , . C-c a L : (1) , (2) C, ( ), (3) . , , , .
9 : . , , . . , , - , org, , C-c a a, , , TODO, A. From / . , , -, , , . !