Hi Bernt, Bernt Hansen wrote: > Eeek! > > I'm not running into this (as far as I know) in my current setup but I > vote we just revert the clocking restriction patches. There are other > unresolved issues with these patches that I've seen and don't currently > have a fix for. > > Please revert the following commits (again). Sorry :( > > - 7a73e15 (Remove file restrictions when generating clock report data, > 2012-01-09) > - e8f93a75 (Honour existing restrictions when visiting tasks from the > agenda, 2011-12-30) > - c41a6f5 (Honour existing restrictions when clocking in from the agenda, > 2011-12-30) > - a0a26cd (Honour existing restrictions when regenerating the agenda, > 2011-12-30)
FYI, I have the (subjective) impression that the below bug just came up a couple of days ago. I would say less than one calendar week. But I may be wrong. >> After clocking in from the agenda -- (org-agenda-clock-in) -- the file >> looks like this: >> >> * A headline >> SCHEDULED: <2012-01-18 Wed +1d> >> >> :LOGBOOK: >> CLOCK: [2012-01-19 Thu 07:19] >> CLOCK: [2012-01-18 Wed 20:10]--[2012-01-19 Thu 07:18] => 11:08 >> >> :END: >> >> :PROPERTIES: >> :HELLO: there >> >> :END: >> * And another >> >> :PROPERTIES: >> :NOW: and again >> >> :END: Best regards, Seb -- Sebastien Vauban
