Milan Glacier <[email protected]> writes: > When using Org Mode, I often face this scenario: I completed a > recurring TODO task (e.g., with a `+1w` repeater) a few days ago, but > I forgot to mark it as DONE at that time. > > If I mark it as DONE today using `C-c C-t`, Org Mode naturally uses > the **current time** for the completion timestamp in the > Logbook. Consequently, the next occurrence’s DEADLINE/SCHEDULED date > is calculated based on today, pushing the schedule forward > incorrectly, rather than based on the actual completion date. > ... > Previously, I had to manually edit the timestamp in the Logbook and > calculate the next deadline by hand, which is quite tedious. > ... > *Discussion:* > > I believe this “retroactive completion” is a fairly common use > case. While my advice-based approach works, it feels like a hack. > > I am interested to know: > 1. Do others find this feature useful? > 2. Could we consider adding an official mechanism to the core > `org-todo` logic to support this? Perhaps a prefix argument or a > configuration option that prompts for a time before marking a task > as done?
Take a look at https://list.orgmode.org/orgmode/[email protected]/ That patch is exactly what you are trying to do. If you address the comments I raised during the review and submit an updated patch there, it will be quickly merged. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
