From: REN Lifeng <renlifeng@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Bug: (org-clock-in 64) leads to redundant clock entries [7.9.3f (release_7.9.3f-17-g7524ef @ /usr/share/emacs/24.3/lisp/org/)]
Date: Wed, 27 Aug 2014 16:23:10 +0800 [thread overview]
Message-ID: <CAN-kwAn9Qii66J7-27EW-2PwRehpt68vZAB0Af-tQCPHADBN-w@mail.gmail.com> (raw)
Hi,
Maybe I missed something obvious, but I find c-u c-u c-u c-c c-x c-i does
not work as the docstring says. Steps to reproduce the problem follows.
- emacs -q
- (find-file "test.org")
- insert a header, clock in (say 15:39)
- clock out after more than 1 minute (say 15:43)
- insert another header
- (org-clock-in 64)
I expect there be one and only one clock entry (15:43). But what I got was 2
entries. The org file is something like the following.
* head one
CLOCK: [2014-08-27 Wed 15:39]--[2014-08-27 Wed 15:43] => 0:04
* (org-clock-in 64) leads to redundant clock entry
CLOCK: [2014-08-27 Wed 15:44]
CLOCK: [2014-08-27 Wed 15:43]
The following lines in org-clock.el bother me a little.
(when (equal select '(64))
;; Set start-time to `org-clock-out-time'
(let ((org-clock-continuously t))
(org-clock-in nil org-clock-out-time)))
Why does it call itself recursively instread of simply setting parameter
start-time to org-clock-out-time?
Emacs : GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.12.2)
of 2014-06-07 on barber, modified by Debian
Package: Org-mode version 7.9.3f (release_7.9.3f-17-g7524ef @
/usr/share/emacs/24.3/lisp/org/)
--
REN Lifeng
next reply other threads:[~2014-08-27 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 8:23 REN Lifeng [this message]
2014-08-28 9:52 ` Bug: (org-clock-in 64) leads to redundant clock entries [7.9.3f (release_7.9.3f-17-g7524ef @ /usr/share/emacs/24.3/lisp/org/)] Nicolas Goaziou
2014-08-29 2:06 ` REN Lifeng
2014-08-29 10:01 ` Nicolas Goaziou
2014-08-29 13:41 ` REN Lifeng
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=CAN-kwAn9Qii66J7-27EW-2PwRehpt68vZAB0Af-tQCPHADBN-w@mail.gmail.com \
--to=renlifeng@gmail.com \
--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).