Re: Clocking in the current task should clock it out first

[John Wiegley <jwiegley@gmail.com>]

On Mar 22, 2010, at 8:25 PM, Bernt Hansen wrote:

> I can't get the clock resolution/idle time code to do anything really
> useful in my setup.  If I do org-resolve-clocks when my current task is
> clocking it asks for how many minutes to keep etc, and then clocks in
> from *now* leaving a hole in my clock data which I don't want.
> 
> I'm not sure exactly how this stuff is supposed to work - maybe John can
> shed some light on this.  I can't find documentation about resolving
> clocks in the regular org-mode documentation either.  I remember an
> article John posted on the mailing list but I don't think that got into
> the official org-mode documentation other than the lisp functions and
> docstrings.

Can you be a bit clearer here, Bernt?  I use the clock resolver constantly and have not been having the kinds of problem you describe.  I'd like to get these hammered out now, though.

> I have also notice that clock resolution (in the distant past) would
> overlap clock times.  If it finds more than one open clock it can
> resolve them so that they overlap with other clock entries and for me
> that's _really_ _really_ bad.  I'd rather have it to nothing than create
> hard-to-find overlapping clock entries.

Yes, this is a possibility. :(  Org-mode doesn't handle multiple open clocks gracefully in other ways too, so I didn't try to hard to avoid situations like these in the resolver.

John