From: Kyle Meyer <kyle@kyleam.com>
To: "Tory S. Anderson" <torys.anderson@gmail.com>
Cc: orgmode list <emacs-orgmode@gnu.org>
Subject: Re: org-clock-persistence-insinuate not working anymore (25.0.5)
Date: Mon, 25 May 2015 14:39:45 -0400 [thread overview]
Message-ID: <87twv01oy6.fsf@kyleam.com> (raw)
In-Reply-To: <87pp5o91ve.fsf@gmail.com> (Tory S. Anderson's message of "Mon, 25 May 2015 10:18:45 -0400")
[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]
torys.anderson@gmail.com (Tory S. Anderson) wrote:
> I've been using the following code for several months to make it easy
> to clock back in to my frequent tasks as I track my time usage:
>
> (org-clock-persistence-insinuate)
> (setq org-clock-persist t)
>
> A few days ago I updated emacs to the dev master and my clock is no
> longer persisting; the list of recent tasks is perpetually "nil". Any
> ideas on how to fix this, or what happened?
torys.anderson@gmail.com (Tory S. Anderson) wrote:
> How about any suggestions on how to debug this, since it isn't
> actually throwing any errors (and I'm a novice emacs-debugger)? The
> tasks list will contain "interrupted task" and "recent task" but none
> of the actual task names. (this comes from passing a single arg to
> org-clock-in)
Since you think it was a recent change that is causing problems, you
could try some combination of the following.
- In the Emacs source directory, run 'git log -- lisp/org/org-clock.el'
to see what's been done recently in the file.
- Come up with a minimum test config and Org file that you can run with
'emacs -Q'.
- Run 'git bisect' between HEAD and the last commit that you know was
behaving. Come up with a simple test using the minimal configuration
above to see if a given revision is good or bad.
- When you find a function that you suspect is causing issues, run
eval-defun with EDEBUG-IT (C-u C-M-x) and walk through the call of
that function.
I've been unable to reproduce the problem using a Emacs from a recent
commit (ac59d538982d040c) with the attached test files.
If I run
emacs -Q -l org-clock-persistent.el
and clock in to the heading in org-clock-persistent.org and then kill
Emacs, the values in org-clock-save.el are non-nil. Restarting emacs
with the command above and opening org-clock-persistent.org offers to
resume.
[-- Attachment #2: org-clock-persistent.el --]
[-- Type: application/emacs-lisp, Size: 121 bytes --]
[-- Attachment #3: org-clock-persistent.org --]
[-- Type: text/plain, Size: 4 bytes --]
* h
[-- Attachment #4: Type: text/plain, Size: 60 bytes --]
Can you reproduce the problem if you do the same?
--
Kyle
prev parent reply other threads:[~2015-05-25 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 20:08 org-clock-persistence-insinuate not working anymore (25.0.5) Tory S. Anderson
2015-05-25 14:18 ` Tory S. Anderson
2015-05-25 18:39 ` Kyle Meyer [this message]
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=87twv01oy6.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=torys.anderson@gmail.com \
/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).