Hi Stig, Thanks for your feedback!
>> https://gitlab.com/marcowahl/hack-time is a little tool to forge the >>[...] >> Comments welcome, as always. > > I gave it a quick spin. The first thing that struck me was sadness at > not finding an elpa package :-( You are right, I think. I'll propose the hack-time code soon as elpa package. Possibly in the form of a minor mode. You are invited to contribute to the realization as package. > Anyway, I obtained it from its repo and I positioned calendar on 7th of > February, and invoked it on an entry I forgot to mark as done yesterday. > This is the result: > > ,---- > | ** TODO Practice guitar > | SCHEDULED: <2017-02-08 Wed ++1d/3d> > | :PROPERTIES: > | :STYLE: habit > | :LAST_REPEAT: [2017-02-08 Tue 12:01] > | :END: > | :LOGBOOK: > | - State "DONE" from "TODO" [2017-02-07 Tue 11:55] \\ > `---- > > Note that: > > - new scheduled time is correct > - logbook entry is correct > - LAST_REPEAT property is *incorrect*; I expect this too to be > [2017-02-07 Tue 11:55] Yes. I also noticed the issue with LAST_REPEAT. I should have told in the announcement that 'hack-time' depends on the Org 'master' branch since about two weeks to handle LAST_REPEAT reliably. Unfortunately 'hack-time' in its current form is not strong enough to hack ANY time in Emacs. Up to now 'hack-time' only applies to elisp code when it calls 'current-time'. Best regards, Marco