From: Carsten Dominik <firstname.lastname@example.org>
To: Matthew Lundin <email@example.com>
Cc: firstname.lastname@example.org, Carsten Dominik <email@example.com>
Subject: Re: Changing TODO state to DONE does not stop clock in frame
Date: Sun, 22 Mar 2009 16:45:41 +0100 [thread overview]
Message-ID: <3144EAA7-8ABF-4AC7-B31E-2733031A024D@uva.nl> (raw)
On Mar 21, 2009, at 9:43 PM, Matthew Lundin wrote:
>> 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
>>> and doing the same thing there on the same item does stop the clock.
> Carsten Dominik <firstname.lastname@example.org> 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
> 1. Clocked into an item.
> 2. Created an indirect buffer.
> 3. Clocked out within the indirect buffer.
I am still unable to reproduce this.
next prev parent reply other threads:[~2009-03-22 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 12:26 Changing TODO state to DONE does not stop clock in frame Chris Randle
2009-03-21 12:57 ` Carsten Dominik
2009-03-21 20:43 ` Matthew Lundin
2009-03-22 15:45 ` Carsten Dominik [this message]
2009-03-23 11:07 ` Sebastian Rose
2009-03-23 12:44 ` Chris Randle
2009-03-23 13:50 ` Bernt Hansen
2009-03-23 20:04 ` Carsten Dominik
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).