From: hymie@lactose.homelinux.net (hymie!)
To: emacs-orgmode@gnu.org
Subject: Re: clock-in clock-out problems
Date: Mon, 18 Aug 2014 19:02:10 +0000 (UTC) [thread overview]
Message-ID: <lstiji$5dn$1@ger.gmane.org> (raw)
In-Reply-To: 87siktslfr.fsf@snow.nl
In our last episode, the evil Dr. Lacto had captured our hero,
Joost Helberg <joost@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 hymie@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
next prev parent reply other threads:[~2014-08-18 19:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 15:40 clock-in clock-out problems hymie!
2014-08-18 18:26 ` Joost Helberg
2014-08-18 19:02 ` hymie! [this message]
2014-08-18 20:10 ` Nick Dokos
2014-08-18 20:18 ` Nick Dokos
2014-08-18 20:55 ` hymie!
2014-08-18 21:39 ` Nick Dokos
2014-08-19 3:23 ` hymie!
2014-08-19 15:01 ` hymie!
2014-08-19 15:51 ` Nick Dokos
2014-08-19 18:21 ` hymie!
2014-08-19 20:46 ` hymie!
2014-08-19 22:42 ` Nick Dokos
2014-08-22 13:55 ` Bastien
2014-08-19 7:55 ` Sebastien Vauban
2014-08-19 12:32 ` Nick Dokos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='lstiji$5dn$1@ger.gmane.org' \
--to=hymie@lactose.homelinux.net \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).