From: Jeff Kowalczyk <jtk@yahoo.com>
To: emacs-orgmode@gnu.org
Subject: org-clock-save.el state unwanted Resume clock prompt
Date: Sat, 17 Aug 2013 05:22:08 +0000 (UTC) [thread overview]
Message-ID: <loom.20130817T071624-574@post.gmane.org> (raw)
When opening any org mode files or using M-x org-mode on a
buffer, I get the following prompt:
: Resume clock (bsmith re: status update) (y or n) n
Which refers to a specific heading in one specific org file, used
all day most days.
: ** DONE bsmith re: status update
: CLOSED: [2013-08-06 Tue 13:12]
: :LOGBOOK:
: CLOCK: [2013-08-06 Tue 12:53]--[2013-08-06 Tue 13:12] => 0:19
: :END:
The cause of the prompt is easily found (org-clock-save.el,
source wrapped):
: ;; org-persist.el - myhost at <2013-08-06 Tue 13:42>
: (setq resume-clock '("/home/jtk/org/upwind.org" . 2049565))
:
: (setq stored-clock-history
: '(("/home/myuser/org/acme.org" . 2044203)
: ("/home/myuser/org/acme.org" . 2044243)
: ("/home/myuser/org/acme.org" . 2046954)
: ("/home/myuser/org/acme.org" . 2049576)
: ("/home/myuser/org/acme.org" . 2049494)))
The above headline corresponds to the last position character
mark, 2049494.
My questions are:
- What's different about that heading that it isn't closed?
- Is there another lisp source of clock insinuate data besides
org-persist.el?
- What lisp data edit operation would safely clear the
open clock status?
On a few occasions I've deleted org-clock-save.el to clear
the problem, and had a recurrence on a different heading some
weeks later. There could be some behavior related to running
clocks when emacs daemon stops abruptly on system or X
shutdown.
Thanks,
Jeff
next reply other threads:[~2013-08-17 5:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-17 5:22 Jeff Kowalczyk [this message]
2013-10-29 8:33 ` org-clock-save.el state unwanted Resume clock prompt Sebastien Vauban
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=loom.20130817T071624-574@post.gmane.org \
--to=jtk@yahoo.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).