From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kyle Meyer Subject: Re: org-clock-persistence-insinuate not working anymore (25.0.5) Date: Mon, 25 May 2015 14:39:45 -0400 Message-ID: <87twv01oy6.fsf@kyleam.com> References: <87h9r33vlf.fsf@gmail.com> <87pp5o91ve.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52728) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YwxIJ-0000Uh-Bx for emacs-orgmode@gnu.org; Mon, 25 May 2015 14:40:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YwxIE-0001qQ-9B for emacs-orgmode@gnu.org; Mon, 25 May 2015 14:40:11 -0400 Received: from mail-qg0-f52.google.com ([209.85.192.52]:34071) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YwxID-0001ku-SG for emacs-orgmode@gnu.org; Mon, 25 May 2015 14:40:05 -0400 Received: by qgez61 with SMTP id z61so49405064qge.1 for ; Mon, 25 May 2015 11:40:04 -0700 (PDT) In-Reply-To: <87pp5o91ve.fsf@gmail.com> (Tory S. Anderson's message of "Mon, 25 May 2015 10:18:45 -0400") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "Tory S. Anderson" Cc: orgmode list --=-=-= Content-Type: text/plain 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. --=-=-= Content-Type: application/emacs-lisp Content-Disposition: attachment; filename=org-clock-persistent.el Content-Transfer-Encoding: quoted-printable (setq org-clock-persist t) (setq org-clock-persist-file "/tmp/org-clock-save.el") (org-clock-persistence-insinuate) --=-=-= Content-Type: text/plain Content-Disposition: attachment; filename=org-clock-persistent.org * h --=-=-= Content-Type: text/plain Can you reproduce the problem if you do the same? -- Kyle --=-=-=--