From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthew Lundin <mdl@imapmail.org>
Subject: Re: Changing TODO state to DONE does not stop clock in frame
Date: Sat, 21 Mar 2009 15:43:20 -0500
Message-ID: <m2tz5md2tz.fsf@fastmail.fm>
References: <F3B1B71B336C42B58EC207AA7D652E5B@CUBE>
	<1FA17072-1917-414E-8AA8-2084343E97AB@uva.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Ll82T-0006zT-F2
	for emacs-orgmode@gnu.org; Sat, 21 Mar 2009 16:43:29 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Ll82N-0006z9-TW
	for emacs-orgmode@gnu.org; Sat, 21 Mar 2009 16:43:27 -0400
Received: from [199.232.76.173] (port=48150 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Ll82N-0006z6-MS
	for emacs-orgmode@gnu.org; Sat, 21 Mar 2009 16:43:23 -0400
Received: from out2.smtp.messagingengine.com ([66.111.4.26]:32989)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <lundin@fastmail.fm>) id 1Ll82N-0005ea-Bu
	for emacs-orgmode@gnu.org; Sat, 21 Mar 2009 16:43:23 -0400
In-Reply-To: <1FA17072-1917-414E-8AA8-2084343E97AB@uva.nl> (Carsten Dominik's
	message of "Sat\, 21 Mar 2009 13\:57\:53 +0100")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org


> On Mar 19, 2009, at 1:26 PM, Chris Randle wrote:

>> I've noticed that, when working in the new frame, changing the TODO
>> state of any item within the frame to DONE (when it is the currently
>> clocked in item) does not stop the clock. Going back to my main frame
>> and doing the same thing there on the same item does stop the clock.

Carsten Dominik <dominik@science.uva.nl> writes:

> I am no able to reproduce this.  Can anyone else try, please?
>
> - Carsten

I just tested it (with org from the git repo). The problem seems to
occur when a clock is started on an item before the indirect buffer is
created. In other words, the clock did not stop when I followed these
steps:

   1. Clocked into an item.

   2. Created an indirect buffer.

   3. Clocked out within the indirect buffer.

The clock did stop when I *both* clocked in and out within the indirect
buffer.

- Matt