From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bernt Hansen <bernt@norang.ca>
Subject: Re: Capture - stay clocked in?
Date: Mon, 07 Mar 2011 10:20:25 -0500
Message-ID: <871v2jc5za.fsf@norang.ca>
References: <AANLkTikTPWsi4v42i_EdjQvouQ7V_ZvU=9zTxH88ppQi@mail.gmail.com>
	<87zkp9f6m8.fsf@gnu.org> <87k4gb1u27.fsf@norang.ca>
	<87aah7nxuf.fsf@gnu.org> <838vwrb5as.fsf@yahoo.it>
	<87ipvvtedy.fsf@gnu.org>
	<1601089B-9879-4C7C-BF74-D6010BE52C5A@gmail.com>
	<87pqq30z28.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from [140.186.70.92] (port=39256 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PwcF0-0008B4-78
	for emacs-orgmode@gnu.org; Mon, 07 Mar 2011 10:21:42 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bernt@norang.ca>) id 1PwcEa-0000Ry-7d
	for emacs-orgmode@gnu.org; Mon, 07 Mar 2011 10:20:35 -0500
Received: from mho-01-ewr.mailhop.org ([204.13.248.71]:32128)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bernt@norang.ca>) id 1PwcEa-0000Rc-5a
	for emacs-orgmode@gnu.org; Mon, 07 Mar 2011 10:20:32 -0500
In-Reply-To: <87pqq30z28.fsf@gnu.org> (Bastien's message of "Mon, 07 Mar 2011
	15:45:19 +0100")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/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: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>, Carsten Dominik <carsten.dominik@gmail.com>

Bastien <bzg@altern.org> writes:

> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> Also, this new property, when set, does not allow :clock-resume,
>> I have not checked if something bad would happen should a user
>> give both by accident.
>
> Ah yes, thanks for bringing this up: :clock-keep has precedence 
> over :clock-resume -- when both are non-nil, :clock-resume will
> be discarded.   I mentioned this in the manual.

For my 't' capture template with :clock-in and :clock-resume (and
no :clock-keep) when I start capture mode for the task when the clock is
not running it stays running in that task (as reported earlier) - Isn't
that a bug?

Thanks,
-- 
Bernt