Re: [O] clock-in clock-out problems

2014-08-22 Thread Bastien
Nick Dokos writes: > OK - glad it's working. It was a pretty weird bug. Thanks for taking care of this! -- Bastien

Re: [O] clock-in clock-out problems

2014-08-19 Thread Nick Dokos
hy...@lactose.homelinux.net (hymie!) writes: > OK. > > I downloaded emacs v 24.4.50.1 . > > I think I still had the problem the first time I ran it, but now I'm not > sure if maybe I ran the old version by mistake. > > Anyway, I commented out my entire .emacs file, run 24.4.50.1, and > the clock p

Re: [O] clock-in clock-out problems

2014-08-19 Thread hymie!
OK. I downloaded emacs v 24.4.50.1 . I think I still had the problem the first time I ran it, but now I'm not sure if maybe I ran the old version by mistake. Anyway, I commented out my entire .emacs file, run 24.4.50.1, and the clock persistence worked. I restored my .emacs a few lines at a tim

Re: [O] clock-in clock-out problems

2014-08-19 Thread hymie!
In our last episode, the evil Dr. Lacto had captured our hero, Nick Dokos , who said: >hy...@lactose.homelinux.net (hymie!) writes: > >> IMPORTANT NEW DISCOVERY >> >> When I use emacs as an X program, the clock persistence works successfully >> and I do not get any errors. >> >> Only when I use e

Re: [O] clock-in clock-out problems

2014-08-19 Thread Nick Dokos
hy...@lactose.homelinux.net (hymie!) writes: > 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

Re: [O] clock-in clock-out problems

2014-08-19 Thread hymie!
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

Re: [O] clock-in clock-out problems

2014-08-19 Thread Nick Dokos
Sebastien Vauban writes: > Nick Dokos wrote: >> I added the following to my .emacs >> >> (require 'org-clock) >> (setq org-clock-persist t) >> (org-clock-persistence-insinuate) >> >> I then start a clock, exit, restart emacs, get asked the "Resume >> clock" question, say "y", work for a while, st

Re: [O] clock-in clock-out problems

2014-08-19 Thread Sebastien Vauban
Nick Dokos wrote: > I added the following to my .emacs > > (require 'org-clock) > (setq org-clock-persist t) > (org-clock-persistence-insinuate) > > 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 O

Re: [O] clock-in clock-out problems

2014-08-18 Thread hymie!
In our last episode, the evil Dr. Lacto had captured our hero, Nick Dokos , who said: >hy...@lactose.homelinux.net (hymie!) writes: > >> (This is the "Messages" that you asked for in the other post) >> >> ("emacs" "zz.org") >> For information about GNU Emacs and the GNU system, type C-x h C-a. >>

Re: [O] clock-in clock-out problems

2014-08-18 Thread Nick Dokos
hy...@lactose.homelinux.net (hymie!) writes: >>> (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 (conc

Re: [O] clock-in clock-out problems

2014-08-18 Thread hymie!
In our last episode, the evil Dr. Lacto had captured our hero, Nick Dokos , who said: >hy...@lactose.homelinux.net (hymie!) writes: > >> In our last episode, the evil Dr. Lacto had captured our hero, >> Joost Helberg , who said: >>>Dear Hymie, >>> >>>The customizable variable: >>> org-clock-pe

Re: [O] clock-in clock-out problems

2014-08-18 Thread Nick Dokos
Nick Dokos writes: > (message "Matched %s" (match-string 1)) Also check your *Messages* buffer to see what matched. > (setq ts (concat "[" (match-string 1) "]")) > (goto-char (match-end 1))<<< apparently > (match-end 1) returned nil

Re: [O] clock-in clock-out problems

2014-08-18 Thread Nick Dokos
hy...@lactose.homelinux.net (hymie!) writes: > In our last episode, the evil Dr. Lacto had captured our hero, > Joost Helberg , 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 g

Re: [O] clock-in clock-out problems

2014-08-18 Thread hymie!
In our last episode, the evil Dr. Lacto had captured our hero, Joost Helberg , 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" th

Re: [O] clock-in clock-out problems

2014-08-18 Thread Joost Helberg
Dear Hymie, The customizable variable: org-clock-persist is used for solving this. regards, Joost BTW: why do you leave emacs? >>>>> "hymie!" == hymie! writes: > From: hymie! > To: emacs-orgmode@gnu.org > Subject: [O] clock-in clock-out problems

[O] clock-in clock-out problems

2014-08-18 Thread hymie!
Greetings. 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 0