Hello,
I just noticed a bug in the clock resolver while testing its
functionality which can be reproduced as follows:
- Start the clock on a task which doesn't contain any clocked time
(i.e. no clock-entries in the :LOGBOOK: property).
- Leave emacs idle until the resolver gets active (I set my
'org-clock-idle-time' to '1', maybe that's the cause of the bug)
- Cancel the clock altogether (i.e. choose 'C' in the resolver), so
that any clock information gets erased from the tasks'
:LOGBOOK:.
- If you now leave emacs idle again, the resolver gets active
although no clock is running
At first I thought that this has something to do with my rather
unusual setting of 'org-clock-idle-time' to '1', but this can also be
reproduced with other settings (though I must confess that I just
tested a value of '2' additionally).
Unfortunately I'm an elisp-illiterate so that I can not look into it
myself.
Kind regards,
Simon
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
address@hidden
http://lists.gnu.org/mailman/listinfo/emacs-orgmode