Hello, Josh Moller-Mara <j...@cns.nyu.edu> writes:
> Recently I've found that clocking in to a repeating task is giving me an > incorrect "task time since last repeat". Normally, when I clock into a task, > mark it as done, and clock in again, I expect the starting clock time to > be 0. In this example: > > * TODO Stuff > SCHEDULED: <2017-08-04 Fri +1d> > :PROPERTIES: > :LAST_REPEAT: [2017-07-12 Wed 20:02] > :END: > :LOGBOOK: > - State "DONE" from "TODO" [2017-07-12 Wed 20:02] > CLOCK: [2017-07-12 Wed 19:54]--[2017-07-12 Wed 20:02] => 0:08 > - State "DONE" from "TODO" [2017-07-08 Sat 19:14] > CLOCK: [2017-07-08 Sat 18:49]--[2017-07-08 Sat 19:14] => 0:25 > - State "DONE" from "TODO" [2017-06-05 Mon 15:14] > CLOCK: [2017-06-05 Mon 14:48]--[2017-06-05 Mon 15:14] => 0:26 > :END: > > clocking in reports that I've spent 8 minutes on the item already, even > though that happened before the LAST_REPEAT. When looking at > (org-clock-sum-current-item (org-clock-get-sum-start)) > I'm getting "8" when I should get "0". > > This change seems to have started happening after commit 112c5ba47, > which changed org-clock-sum to do something different with daylights > savings. Fixed. Thank you. Regards, -- Nicolas Goaziou
