From mboxrd@z Thu Jan  1 00:00:00 1970
From: Joost Helberg <joost@snow.nl>
Subject: Re: clock-in clock-out problems
Date: Mon, 18 Aug 2014 20:26:05 +0200
Message-ID: <87siktslfr.fsf@snow.nl>
References: <lst6p2$ao2$1@ger.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:56633)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <joost@snow.nl>) id 1XJReO-0008Mm-5R
	for emacs-orgmode@gnu.org; Mon, 18 Aug 2014 14:27:29 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <joost@snow.nl>) id 1XJReI-0002m3-35
	for emacs-orgmode@gnu.org; Mon, 18 Aug 2014 14:27:24 -0400
Received: from mx.snow.nl ([213.154.248.146]:38654)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <joost@snow.nl>) id 1XJReH-0002lQ-Q2
	for emacs-orgmode@gnu.org; Mon, 18 Aug 2014 14:27:18 -0400
In-reply-to: <lst6p2$ao2$1@ger.gmane.org>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: hymie! <hymie@lactose.homelinux.net>
Cc: emacs-orgmode@gnu.org

Dear Hymie,

The customizable variable: 
 org-clock-persist

is used for solving this.

regards,

Joost

BTW: why do you leave emacs?

>>>>> "hymie!" == hymie!  <hymie@lactose.homelinux.net> writes:
 > From: hymie! <hymie@lactose.homelinux.net>
 > To: emacs-orgmode@gnu.org
 > Subject: [O] clock-in clock-out problems
 > Date: 2014-08-18T17:40:19+0200

 > 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 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    hymie@lactose.homelinux.net



-- 
Snow B.V.