Re: clock resolver never stops if task hasn't been clocked before

From: Carsten Dominik <carsten.dominik@gmail.com>
To: Simon Campese <simon.campese@uni-dortmund.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: clock resolver never stops if task hasn't been clocked before
Date: Thu, 11 Mar 2010 18:22:39 +0100	[thread overview]
Message-ID: <378BE0FB-8B4B-4EAE-AB64-376792C67C99@gmail.com> (raw)
In-Reply-To: <20100228073149.GA7759@rman-server.rman>

Hi Simon,

somehow I don't seem to be able to reproduce this bug.  Maybe I don't  
have some of your settings?  How about a minimal file and a  
minimal .emacs, or a full bug report according to the manual?

- Carsten

On Feb 28, 2010, at 8:31 AM, Simon Campese wrote:

> 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.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

- Carsten