From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: clock resolver never stops if task hasn't been clocked before Date: Thu, 11 Mar 2010 18:22:39 +0100 Message-ID: <378BE0FB-8B4B-4EAE-AB64-376792C67C99@gmail.com> References: <20100228073149.GA7759@rman-server.rman> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NpmPi-0002GM-Jg for emacs-orgmode@gnu.org; Thu, 11 Mar 2010 12:43:14 -0500 Received: from [140.186.70.92] (port=54024 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NpmPe-00025U-OA for emacs-orgmode@gnu.org; Thu, 11 Mar 2010 12:43:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NpmPZ-00078Q-Jy for emacs-orgmode@gnu.org; Thu, 11 Mar 2010 12:43:06 -0500 Received: from ey-out-1920.google.com ([74.125.78.150]:17842) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NpmPZ-000788-FW for emacs-orgmode@gnu.org; Thu, 11 Mar 2010 12:43:05 -0500 Received: by ey-out-1920.google.com with SMTP id 3so18193eyh.2 for ; Thu, 11 Mar 2010 09:43:04 -0800 (PST) In-Reply-To: <20100228073149.GA7759@rman-server.rman> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Simon Campese Cc: emacs-orgmode@gnu.org 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