In our last episode, the evil Dr. Lacto had captured our hero, Joost Helberg <jo...@snow.nl>, who said: >Dear Hymie, > >The customizable variable: > org-clock-persist > >is used for solving this.
Thanks for the info. However, when I tried it out, I get asked "Resume clock (test) (y or n)" If I answer "n" then the problem recurs (as I would expect). If I answer "y", then I get an error (lines cut to 75-ish, but I can try to send the full entire error message if needed) Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil) goto-char(nil) (cond ((and org-clock-in-resume (looking-at (concat "^[ ]*" org-cloc (save-restriction (widen) (goto-char target-pos) (org-back-to-heading t) ( (save-excursion (save-restriction (widen) (goto-char target-pos) (org-back (save-excursion (if (and selected-task (marker-buffer selected-task)) (pro (let ((interrupting (and (not org-clock-resolving-clocks-due-to-idleness) (catch (quote abort) (let ((interrupting (and (not org-clock-resolving-clo org-clock-in() [...] In either case, "No active clock." I'm honestly not sure in what circumstances I would **not** want the clock to be persistent, but oh well. >BTW: why do you leave emacs? There is a certain flame war that I do not wish to invoke. Let's just say that I've been using a different editor for xxVIi years and I've grown accustomed to it. The only thing I currently use emacs for is org-mode. But sometimes I have to log out. Sometimes my work network drops and it logs me out for me. Sometimes I move from machine to machine and have to edit my files from elsewhere. There are tons of reasons why I can't just leave emacs running. --hymie! http://lactose.homelinux.net/~hymie hy...@lactose.homelinux.net > > > I've discovered a problem with clocking-in and clocking-out. I think > > this used to work in the past (when I ran 8.2.7a and/or 8.2.7b), but > > I've had the same problem twice (both with 8.2.7c) . > > > I have a TODO scheduled for today: > > * TODO run clamav on machine > > SCHEDULED: <2014-08-18 Mon 09:00> > > > I get to work and start it with C-c C-x C-i > > * TODO run clamav on machine > > SCHEDULED: <2014-08-18 Mon 09:00> > > CLOCK: [2014-08-18 Mon 08:55] > > > I save the file, exit emacs, and go off to do other things that may or > > may not include playing larn. This seems to be the important part > > (saving and exiting the file, not playing larn). > > > I get back to my desk, run emacs, and try to clock out of the task > > with C-c C-x C-o. I get an error "No active clock". I get this same > > error whether my cursor is on the "TODO" line or the "CLOCK" line. > > > Now it gets weird. I try to clock in again with C-c C-x C-i. > > I get a warning of a "Dangling clock started 60 minutes ago" and > > I'm asked to "Select a Clock Resolution Command". So clearly it > > sees that there is an open clock that needs to be resolved somehow, > > except C-c C-x C-o still maintains "No active clock." > > > I don't have the self-confidence to ask "How do I file a bug report?" > > Instead I will ask "What did I do wrong?" > > > --hymie! http://lactose.homelinux.net/~hymie