[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] clock-in clock-out problems
From: |
Nick Dokos |
Subject: |
Re: [O] clock-in clock-out problems |
Date: |
Mon, 18 Aug 2014 16:10:30 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux) |
address@hidden (hymie!) writes:
> In our last episode, the evil Dr. Lacto had captured our hero,
> Joost Helberg <address@hidden>, 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 added the following to my .emacs
--8<---------------cut here---------------start------------->8---
(require 'org-clock)
(setq org-clock-persist t)
(org-clock-persistence-insinuate)
--8<---------------cut here---------------end--------------->8---
I then start a clock, exit, restart emacs, get asked the "Resume
clock" question, say "y", work for a while, stop the clock and
everything seems OK.
Org-mode version 8.3beta (release_8.3beta-245-g3a1fff)
If you get an error, then it might be a bug in your version. Post the
version along with the complete backtrace (preferably using
org-submit-bug-report). Also, include the entry that you are clocking -
the error above seems to come from an inability to match the entry:
--8<---------------cut here---------------start------------->8---
(cond
((and org-clock-in-resume
(looking-at
(concat "^[ \t]*" org-clock-string
" \\[\\([0-9]\\{4\\}-[0-9]\\{2\\}-[0-9]\\{2\\}"
" *\\sw+\.? +[012][0-9]:[0-5][0-9]\\)\\][ \t]*$")))
(message "Matched %s" (match-string 1))
(setq ts (concat "[" (match-string 1) "]"))
(goto-char (match-end 1)) <<<<<<<<<<<<<<< apparently
(match-end 1) returned nil
(setq org-clock-start-time
(apply 'encode-time
(org-parse-time-string (match-string 1))))
(setq org-clock-effort (org-entry-get (point)
org-effort-property))
(setq org-clock-total-time (org-clock-sum-current-item
(org-clock-get-sum-start))))
--8<---------------cut here---------------end--------------->8---
--
Nick
- [O] clock-in clock-out problems, hymie!, 2014/08/18
- Re: [O] clock-in clock-out problems, Joost Helberg, 2014/08/18
- Re: [O] clock-in clock-out problems, hymie!, 2014/08/18
- Re: [O] clock-in clock-out problems,
Nick Dokos <=
- Re: [O] clock-in clock-out problems, Nick Dokos, 2014/08/18
- Re: [O] clock-in clock-out problems, hymie!, 2014/08/18
- Re: [O] clock-in clock-out problems, Nick Dokos, 2014/08/18
- Re: [O] clock-in clock-out problems, hymie!, 2014/08/18
- Re: [O] clock-in clock-out problems, hymie!, 2014/08/19
- Re: [O] clock-in clock-out problems, Nick Dokos, 2014/08/19
- Re: [O] clock-in clock-out problems, hymie!, 2014/08/19
- Re: [O] clock-in clock-out problems, hymie!, 2014/08/19
- Re: [O] clock-in clock-out problems, Nick Dokos, 2014/08/19
- Re: [O] clock-in clock-out problems, Bastien, 2014/08/22