From: Adam Spiers <email@example.com> To: org-mode mailing list <firstname.lastname@example.org> Subject: time-warping - retroactively marking DONE? Date: Tue, 7 Jul 2020 12:26:56 +0100 [thread overview] Message-ID: <email@example.com> (raw) Hi all, I'm looking for a way to retroactively mark a task as having been done at a previous time/date. I know that I can just change the keyword to DONE and then edit the timestamp, but this is tedious when it's a repeating event, e.g.: *** NEXT [#A] meditate 15 minutes every day SCHEDULED: <2020-07-06 Mon 11:30-11:50 .+1d> :PROPERTIES: :LAST_REPEAT: [2020-07-05 Sun 11:13] :ID: 142a639c-e06d-4d4b-ad1c-edcd0d9ba6ce :Effort: 0:20 :STYLE: habit :END: - State "DONE" from "NEXT" [2020-07-05 Sun 10:15] - State "DONE" from "NEXT" [2020-07-04 Sat 10:30] - State "DONE" from "NEXT" [2020-07-03 Fri 10:05] - State "DONE" from "NEXT" [2020-07-02 Thu 11:15] I forgot to mark it as done yesterday, which means that I would have to manually edit /three/ timestamps to log the correct data: 1) the SCHEDULED timestamp, 2) the :LAST_REPEAT: property, and 3) the state change history. If this is not currently possible, would it make sense to write a wrapper around `org-todo', e.g. `org-todo-timewarp' or `org-retroactive-todo', which interactively prompts for a timestamp before invoking `org-todo'? Another possibility would be to add yet another magic prefix argument to `org-todo', but it seems that is already heavily overloaded, so it would have to be 'C-u C-u C-u C-u' which isn't particularly convenient. I can even imagine users occasionally wanting to mark stuff done in the future, e.g. if they have an activity planned for tomorrow while they're offline. So maybe using the word 'retroactive' in the wrapper function name is a bit too limiting. Cheers, Adam
next reply other threads:[~2020-07-07 11:27 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-07 11:26 Adam Spiers [this message] 2020-07-08 4:53 ` Kyle Meyer 2020-07-08 5:52 ` Marcin Borkowski [not found] <firstname.lastname@example.org> 2020-07-08 21:38 ` No Wayman 2020-08-30 0:22 ` Adam Spiers 2020-08-30 1:32 ` No Wayman
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: time-warping - retroactively marking DONE?' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).