From: Josh Moller-Mara <jmm@cns.nyu.edu>
To: emacs-orgmode@gnu.org
Subject: Bug: org-clock-sum-current-item/org-clock-get-sum-start not respecting LAST_REPEAT [9.0.9 (release_9.0.9-697-gb0776e @ /usr/local/share/emacs/site-lisp/org/)]
Date: Fri, 04 Aug 2017 12:16:45 +0800 [thread overview]
Message-ID: <877eykj7bm.fsf@cns.nyu.edu> (raw)
Hey there,
Recently I've found that clocking in to a repeating task is giving me an
incorrect "task time since last repeat". Normally, when I clock into a task,
mark it as done, and clock in again, I expect the starting clock time to
be 0. In this example:
* TODO Stuff
SCHEDULED: <2017-08-04 Fri +1d>
:PROPERTIES:
:LAST_REPEAT: [2017-07-12 Wed 20:02]
:END:
:LOGBOOK:
- State "DONE" from "TODO" [2017-07-12 Wed 20:02]
CLOCK: [2017-07-12 Wed 19:54]--[2017-07-12 Wed 20:02] => 0:08
- State "DONE" from "TODO" [2017-07-08 Sat 19:14]
CLOCK: [2017-07-08 Sat 18:49]--[2017-07-08 Sat 19:14] => 0:25
- State "DONE" from "TODO" [2017-06-05 Mon 15:14]
CLOCK: [2017-06-05 Mon 14:48]--[2017-06-05 Mon 15:14] => 0:26
:END:
clocking in reports that I've spent 8 minutes on the item already, even
though that happened before the LAST_REPEAT. When looking at
(org-clock-sum-current-item (org-clock-get-sum-start))
I'm getting "8" when I should get "0".
This change seems to have started happening after commit 112c5ba47,
which changed org-clock-sum to do something different with daylights
savings.
I'm currently using
Emacs : GNU Emacs 26.0.50.2 (x86_64-pc-linux-gnu, GTK+ Version 3.22.5)
of 2017-01-18
Package: Org mode version 9.0.9 (release_9.0.9-697-gb0776e @ /usr/local/share/emacs/site-lisp/org/)
Best,
Josh
next reply other threads:[~2017-08-04 4:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 4:16 Josh Moller-Mara [this message]
2017-08-05 13:49 ` Bug: org-clock-sum-current-item/org-clock-get-sum-start not respecting LAST_REPEAT [9.0.9 (release_9.0.9-697-gb0776e @ /usr/local/share/emacs/site-lisp/org/)] Nicolas Goaziou
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=877eykj7bm.fsf@cns.nyu.edu \
--to=jmm@cns.nyu.edu \
--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).