From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bernt Hansen <bernt@norang.ca>
Subject: Re: Capture - stay clocked in?
Date: Sun, 06 Mar 2011 22:35:44 -0500
Message-ID: <87k4gb1u27.fsf@norang.ca>
References: <AANLkTikTPWsi4v42i_EdjQvouQ7V_ZvU=9zTxH88ppQi@mail.gmail.com>
	<87zkp9f6m8.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=45522 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PwREo-0008Ou-6T
	for emacs-orgmode@gnu.org; Sun, 06 Mar 2011 22:36:03 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bernt@norang.ca>) id 1PwREm-00043d-Mr
	for emacs-orgmode@gnu.org; Sun, 06 Mar 2011 22:36:02 -0500
Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:47116)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bernt@norang.ca>) id 1PwREm-00042c-L3
	for emacs-orgmode@gnu.org; Sun, 06 Mar 2011 22:36:00 -0500
In-Reply-To: <87zkp9f6m8.fsf@gnu.org> (Bastien's message of "Sun, 06 Mar 2011
	01:13:51 +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>

Bastien <bzg@altern.org> writes:

> Hi Nathan,
>
> Nathan Neff <nathan.neff@gmail.com> writes:
>
>> Is there an option NOT to clock out of a Todo item that's
>> created using org-capture?
>
> I assume you mean "when :immediate-finish is non-nil in a capture
> template", right?
>
> Yes, this bugged me as well.  
>
> The default behavior is now (latest git) that :immediate-finish t 
> will *not* clock out the captured entry so that you can use it in
> conjunction with :clock-in.
>
> HTH,

Hi Bastien,

I think this change may have changed the default for
non :immediate-finish capture tasks as well.

I have the following template:

--8<---------------cut here---------------start------------->8---
("t" "todo" entry
  (file "~/git/org/refile.org")
  "* TODO %?\n%U\n%a\n" :clock-in t :clock-resume t)
--8<---------------cut here---------------end--------------->8---

and if the clock is not running when I start capture with this template
it stays running afterwards.  I don't think this was the intended
behaviour.

Let me know if you want me to try to isolate the commit that changed
this behaviour for me.

Thanks,
-- 
Bernt