|
|
|
|
|
by TeMPOraL
1247 days ago
|
|
Org Mode supports a simpler and more manual form of this, by giving you three different repeater types on timestamps. See https://orgmode.org/manual/Repeated-tasks.html for official manual, but in short: - <2023-01-23 Mon +6d> - completing a task with such timestamp will move the time forward by 6 days. If you were supposed to do it 20 days ago, you'll have to complete it three times before it's no longer overdue (and becomes scheduled to 4 days from now, i.e. 4x6 - 20). - <2023-01-23 Mon ++6d> - completing a task with such timestamp will move the time forward by however many 6-day increments it takes to get it at least 6 days ahead of now. E.g. if the task is overdue for 20 days, completing it now will make it due in 10 days (four 6-day increments are enough for the due date to be in the future, but you need an extra 6-day increment for due date to be at least 6 days in the future). - <2023-01-23 Mon .+6d> - completing a task with such timestamp will move the due date to 6 days after today. If the task was 20 days overdue and you complete it now, the next due date is in 6 days. These behaviors have some extra variations depending on whether the timestamp contains the hour/minute part, and on what unit is used for the increment - e.g. the difference between ++7d and ++1w is that the latter will ensure the task stays on the same day of the week as previously. |
|