From: Simon Campese <simon.campese@uni-dortmund.de>
To: emacs-orgmode@gnu.org
Subject: clock resolver never stops if task hasn't been clocked before
Date: Sun, 28 Feb 2010 08:31:50 +0100 [thread overview]
Message-ID: <20100228073149.GA7759@rman-server.rman> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 995 bytes --]
Hello,
I just noticed a bug in the clock resolver while testing its
functionality which can be reproduced as follows:
- Start the clock on a task which doesn't contain any clocked time
(i.e. no clock-entries in the :LOGBOOK: property).
- Leave emacs idle until the resolver gets active (I set my
'org-clock-idle-time' to '1', maybe that's the cause of the bug)
- Cancel the clock altogether (i.e. choose 'C' in the resolver), so
that any clock information gets erased from the tasks'
:LOGBOOK:.
- If you now leave emacs idle again, the resolver gets active
although no clock is running
At first I thought that this has something to do with my rather
unusual setting of 'org-clock-idle-time' to '1', but this can also be
reproduced with other settings (though I must confess that I just
tested a value of '2' additionally).
Unfortunately I'm an elisp-illiterate so that I can not look into it
myself.
Kind regards,
Simon
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next reply other threads:[~2010-02-28 7:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 7:31 Simon Campese [this message]
2010-03-11 17:22 ` clock resolver never stops if task hasn't been clocked before 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:
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=20100228073149.GA7759@rman-server.rman \
--to=simon.campese@uni-dortmund.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).