IMPORTANT NEW DISCOVERY

By default, I use emacs in a terminal window (emacs -nw)

When I use emacs as an X program, the clock persistence works successfully
and I do not get any errors.

Only when I use emacs with the -nw flag do I get the clock persistence
error below.

--hymie!    http://lactose.homelinux.net/~hymie    hy...@lactose.homelinux.net

In our last episode, the evil Dr. Lacto had captured our hero,
  hy...@lactose.homelinux.net (hymie!), who said:

>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-clock-string " \\[\\([0-9]\\{4\\}-[0-9]\\{2\\}-[0-9]\\{2\\}" "
>*\\sw+.? +[012][0-9]:[0-5][0-9]\\)\\][         ]*$"))) (message "Matched %s"
>(match-string 1)) (setq ts (concat "[" (match-string 1) "]")) (goto-char
>(match-end 1)) (setq org-clock-start-time (apply (quote 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)))) ((eq
>org-clock-in-resume (quote auto-restart)) (message "Cannot restart clock
>because task does not contain unfinished clock") (ding) (sit-for 2)
>(throw (quote abort) nil)) (t (insert-before-markers "\n")
>(backward-char 1) (org-indent-line) (if (and (save-excursi
> on (end-of-line 0) (org-in-item-p))) (progn (beginning-of-line 1)
>(org-indent-line-to (- (org-get-indentation) 2)))) (insert
>org-clock-string " ") (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))) (setq
>org-clock-start-time (or (and org-clock-continuously org-clock-out-time)
>(and leftover (y-or-n-p (format "You stopped another clock %d mins ago;
>start this one from then? " (/ ... 60))) leftover) start-time
>(org-current-time org-clock-rounding-minutes t))) (setq ts
>(org-insert-time-stamp org-clock-start-time (quote with-hm) (quote
>inactive)))))


Reply via email to