emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Chris Randle" <chris@amlog.co.uk>
To: emacs-orgmode@gnu.org
Subject: Changing TODO state to DONE does not stop clock in frame
Date: Thu, 19 Mar 2009 12:26:31 -0000	[thread overview]
Message-ID: <F3B1B71B336C42B58EC207AA7D652E5B@CUBE> (raw)

Hi Carsten,

Summary: Changing TODO state to DONE does not stop clock in frame

I have one giant Org-mode file for everything. I frequently use `C-c C-x
b' to take the current node and show it in a new frame with narrow
subtree so that I can concentrate on just that region of my file. Rather
like hoist in GrandView, if anyone remembers that.

My Org Manual (6.24b) says "The indirect buffer...will contain the
entire buffer, but will be narrowed to the current tree. Editing the
indirect buffer will also change the original buffer, but without
affecting visibility in that buffer.

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.

I haven't altered `org-clock-out-when-done', and Emacs reports its value
as t.

Is this something that's easily fixed/modified?

Chris Randle
Windows XP Pro SP3 - GNU Emacs 22.1.1 - Org-mode 6.24b

             reply	other threads:[~2009-03-19 12:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19 12:26 Chris Randle [this message]
2009-03-21 12:57 ` Changing TODO state to DONE does not stop clock in frame Carsten Dominik
2009-03-21 20:43   ` Matthew Lundin
2009-03-22 15:45     ` Carsten Dominik
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

Reply instructions:

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 \
    --in-reply-to=F3B1B71B336C42B58EC207AA7D652E5B@CUBE \
    --to=chris@amlog.co.uk \
    --cc=emacs-orgmode@gnu.org \


* 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).