John Hendy <jw.he...@gmail.com> writes: > Could someone fill me in on your process for clocking in things after > the fact? I've been trying to get into to clocking, but, especially at > home, I don't return to my computer in between every different thing. > Instead, I stop at it when I get a pause and try to fill in what I've > been doing. So far, this has been something akin to: > > - create a new sub-headline and call it what I was doing > - C-c C-c to tag it > - C-c C-x C-i followed by C-c C-x C-o to create a clocked time stamps > - Manually edit the times > - C-c C-c to update the count
Not sure if this is entirely relevant here, but I have a similar problem. I often find I need to mark recurring tasks as "done" that I completed on the previous day or even earlier. For most tasks, it doesn't matter when I mark them as done; but if the task uses org-habits, it means I have to manually edit the timestamp so that it doesn't mess up the habit log going forward. If there's a better way to deal with situations like this, I'd love to hear about it. If not, I just wanted to point out another use case for anyone thinking about implementing "retroactive timestamp editing" functions. Thanks! Richard
