From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Wood Subject: Re: org-capture-template :clock-in property not working Date: Tue, 13 Dec 2016 15:13:38 +0000 Message-ID: References: <87k2b47z75.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c0b6d8acd658e05438baa8f Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39658) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cGon7-0007H0-Kp for emacs-orgmode@gnu.org; Tue, 13 Dec 2016 10:14:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cGon3-0004zk-Jm for emacs-orgmode@gnu.org; Tue, 13 Dec 2016 10:14:53 -0500 Received: from mail-vk0-f49.google.com ([209.85.213.49]:32978) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cGon3-0004zc-Ei for emacs-orgmode@gnu.org; Tue, 13 Dec 2016 10:14:49 -0500 Received: by mail-vk0-f49.google.com with SMTP id 137so65716474vkl.0 for ; Tue, 13 Dec 2016 07:14:49 -0800 (PST) In-Reply-To: <87k2b47z75.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Mark Wood , emacs-orgmode@gnu.org --94eb2c0b6d8acd658e05438baa8f Content-Type: text/plain; charset=UTF-8 I did a little more digging. I too can get it to work correctly, so long as there is no Default Clock task identified. However, if I create a default clock task, it appears that the :clock-in property is ignored. I'll try to dig into it a little more, but I can reproduce it every time when there is a default clock. Thanks again for looking at it. On Tue, Dec 13, 2016 at 8:09 AM Nicolas Goaziou wrote: > Hello, > > Mark Wood writes: > > > After recently upgrading to 20161118, I notice that the clock-in property > > in my org-capture-templates is no longer functioning. It appears to > > successfully clock me out of my current task, but that's it. > > > > My capture template is: > > > > (setq org-capture-templates > > '(("t" "Todo" entry (file "/org/refile.org") > > "* TODO %?\n%U\n" :clock-in t :clock-resume t))) > > FWIW I cannot reproduce it, i.e., clock is properly started. > > Regards, > > -- > Nicolas Goaziou > --94eb2c0b6d8acd658e05438baa8f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I did a little more digging.=C2=A0 I too can get it to wor= k correctly, so long as there is no Default Clock task identified.

=
However, if I create a default clock task, it appears that the := clock-in property is ignored.

I'll try to dig = into it a little more, but I can reproduce it every time when there is a de= fault clock.

Thanks again for looking at it.
=

On Tue, Dec 13, 2016 = at 8:09 AM Nicolas Goaziou <ma= il@nicolasgoaziou.fr> wrote:
Hello,

Mark Wood <mjwood0@gmail.com> writes:

> After recently upgrading to 20161118, I notice that the clock-in prope= rty
> in my org-capture-templates is no longer functioning.=C2=A0 It appears= to
> successfully clock me out of my current task, but that's it.
>
> My capture template is:
>
> (setq org-capture-templates
>=C2=A0 =C2=A0 =C2=A0 =C2=A0'(("t" "Todo" entry = (file "/org/refile.org")
> "* TODO %?\n%U\n" :clock-in t :clock-resume t)))

FWIW I cannot reproduce it, i.e., clock is properly started.

Regards,

--
Nicolas Goaziou
--94eb2c0b6d8acd658e05438baa8f--