Re: [O] org-clock-persistence-insinuate not working anymore (25.0.5)

[Kyle Meyer]

address@hidden (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?

address@hidden (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.

org-clock-persistent.el
Description: application/emacs-lisp

org-clock-persistent.org
Description: Text document

Can you reproduce the problem if you do the same?

--
Kyle