From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: Org-mode version 6.31trans; Problem with new 'away time' feature Date: Sat, 24 Oct 2009 15:04:30 +0200 Message-ID: References: <825D1FA3-229B-4F36-B12D-C5CADFA3ABCB@gmail.com> 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 1N1gIT-0003mB-Sx for emacs-orgmode@gnu.org; Sat, 24 Oct 2009 09:04:41 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N1gIO-0003l0-2L for emacs-orgmode@gnu.org; Sat, 24 Oct 2009 09:04:40 -0400 Received: from [199.232.76.173] (port=60195 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N1gIN-0003kh-AM for emacs-orgmode@gnu.org; Sat, 24 Oct 2009 09:04:35 -0400 Received: from ey-out-1920.google.com ([74.125.78.145]:25529) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N1gIM-0001QU-8o for emacs-orgmode@gnu.org; Sat, 24 Oct 2009 09:04:34 -0400 Received: by ey-out-1920.google.com with SMTP id 3so10894909eyh.34 for ; Sat, 24 Oct 2009 06:04:33 -0700 (PDT) In-Reply-To: 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: Kai Tetzlaff Cc: emacs-orgmode@gnu.org On Oct 23, 2009, at 10:20 AM, Kai Tetzlaff wrote: > John Wiegley wrote: >> On Oct 22, 2009, at 6:32 PM, Kai Tetzlaff wrote: >> >>> 'Cannot restart clock because task does not contain unfinished >>> clock' >>> >>> When i look at the corresponding clock line the previously running >>> clock >>> has now indeed been stopped (with a time stamp corresponding to the >>> current time). >> >> This is an interesting bug. It sounds like the point is not being >> moved >> to the correct location to perform the clock-in. I'll take a look. > > I did some additional investigation and found that if i'm clocking > into > an item with an unresolved inactive clock from the agenda (created by > deleting the end time in its most recent CLOCK: line) a similar thing > happens. I'm actually getting clocked out of the current clock and a > new > CLOCK line gets added which is then the running clock. I think this is what sould happen, no? The other problem you reported, where I said this is a conflict with James' code, should be fixed now. Please verify. - Carsten > > Don't know if this helps but stepping through the code in the > debugger i > get to the following code in org-clock-resolve-clock: > > ((eq resolve-to 'now) > (if restart-p > (error "RESTART-P is not valid here")) > (if (or close-p org-clock-clocking-in) <-- org-close: nil, > org-clock-clocking-in: t > (org-clock-clock-out clock fail-quietly) <-- clock-out done here > (unless (org-is-active-clock clock) > (org-clock-clock-in clock t)))) > > > > _______________________________________________ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten