From: Mark Wood <mjwood0@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-capture-template :clock-in property not working
Date: Tue, 13 Dec 2016 15:56:06 +0000 [thread overview]
Message-ID: <CAGAi9Ha8w1N-R==XFMGOow6Fr78T_5T-XCPEt5E+P4Qbf_c3tg@mail.gmail.com> (raw)
In-Reply-To: <CAGAi9HYE__ZvKB53if2x1zom304KozHjYMnR1uGVU0yHyAOmvg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
I believe I found my issue.
It appears I had a hook upon clockout that was causing issues. So sorry to
bother everyone.
On the plus side, I learned some lisp debugging skills.
Thanks again.
On Tue, Dec 13, 2016 at 10:13 AM Mark Wood <mjwood0@gmail.com> wrote:
> 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 <mail@nicolasgoaziou.fr>
> wrote:
>
> Hello,
>
> Mark Wood <mjwood0@gmail.com> 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
>
>
[-- Attachment #2: Type: text/html, Size: 2835 bytes --]
prev parent reply other threads:[~2016-12-13 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 21:57 org-capture-template :clock-in property not working Mark Wood
2016-12-13 13:09 ` Nicolas Goaziou
2016-12-13 15:13 ` Mark Wood
2016-12-13 15:56 ` Mark Wood [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGAi9Ha8w1N-R==XFMGOow6Fr78T_5T-XCPEt5E+P4Qbf_c3tg@mail.gmail.com' \
--to=mjwood0@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).