From: Kai Tetzlaff <kai.tetzlaff@gmx.de>
To: emacs-orgmode@gnu.org
Subject: Re: Org-mode version 6.31trans; Problem with new 'away time' feature
Date: Fri, 23 Oct 2009 10:20:44 +0200 [thread overview]
Message-ID: <hbrp12$5h1$1@ger.gmane.org> (raw)
In-Reply-To: <825D1FA3-229B-4F36-B12D-C5CADFA3ABCB@gmail.com>
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.
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))))
next prev parent reply other threads:[~2009-10-23 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 22:32 Org-mode version 6.31trans; Problem with new 'away time' feature Kai Tetzlaff
2009-10-23 0:38 ` John Wiegley
2009-10-23 8:20 ` Kai Tetzlaff [this message]
2009-10-24 13:04 ` Carsten Dominik
2009-10-24 16:39 ` Kai Tetzlaff
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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='hbrp12$5h1$1@ger.gmane.org' \
--to=kai.tetzlaff@gmx.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).