From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Capture - stay clocked in? Date: Mon, 07 Mar 2011 09:23:04 +0100 Message-ID: <87aah7nxuf.fsf@gnu.org> References: <87zkp9f6m8.fsf@gnu.org> <87k4gb1u27.fsf@norang.ca> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=44589 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PwViv-0005hP-At for emacs-orgmode@gnu.org; Mon, 07 Mar 2011 03:23:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PwViu-00020P-6U for emacs-orgmode@gnu.org; Mon, 07 Mar 2011 03:23:25 -0500 Received: from mail-ww0-f49.google.com ([74.125.82.49]:62691) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PwViu-00020A-02 for emacs-orgmode@gnu.org; Mon, 07 Mar 2011 03:23:24 -0500 Received: by wwj40 with SMTP id 40so4083990wwj.30 for ; Mon, 07 Mar 2011 00:23:23 -0800 (PST) In-Reply-To: <87k4gb1u27.fsf@norang.ca> (Bernt Hansen's message of "Sun, 06 Mar 2011 22:35:44 -0500") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: Bernt Hansen Cc: emacs-orgmode Hi Bernt, Bernt Hansen writes: > I think this change may have changed the default for > non :immediate-finish capture tasks as well. > > I have the following template: > > ("t" "todo" entry > (file "~/git/org/refile.org") > "* TODO %?\n%U\n%a\n" :clock-in t :clock-resume t) > > 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. I see. My first idea was to implement a new template option :immediate-refile (or a similar name). :immediate-finish would stick to the old behavior (no clocking allowed) and :immediate-refile would leave the clock open. But I thought this was potentially confusing. What about :clock-out t, explicitely telling org-capture-finalize to clock out when? -- Bastien