I can reprouce this.
Could this be related to some obsolete configuration values?
I have no buffer-local TODO setup. I always use
(setq org-todo-keywords (quote (TODO STARTED | DONE CANCELED(c@
but still, `org-done-keywords' is nil.
Thus `DONE' is never a member of `org-done-keywords'
Hi Carsten
Carsten Dominik wrote:
I am no able to reproduce this. Can anyone else try, please?
On Mar 19, 2009, at 1:26 PM, Chris Randle wrote:
Summary: Changing TODO state to DONE does not stop clock in frame
Thanks for looking into this for me. I was worried that it may be
something odd
Hi Chris,l
thanks for the walk-through. As usually, that did it.
indeed, there was a bug, which is fixed now.
Thanks also to everyone who contributed with additional checking.
- Carsten
On Mar 23, 2009, at 1:44 PM, Chris Randle wrote:
Hi Carsten
Carsten Dominik wrote:
I am no able to
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
I am no able to reproduce this. Can anyone else try, please?
- Carsten
On Mar 19, 2009, at 1:26 PM, Chris Randle wrote:
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
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
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
