From: Cody Goodman <codygman.consulting@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Override :clock-in (hence org-clock-in) behavior for a specific capture template
Date: Fri, 13 Jul 2018 23:59:50 -0500 [thread overview]
Message-ID: <CADq_+R16-sDByJp0tRhOd-P2w-ZTU58BOjjs33wkLhsykwJqLA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]
Here is my detailed problem exposition exported from org:
1 executive summary
===================
I want to start at a child node and clock into the grandparent rather than
the current child at point in a capture task
2 my capture
============
,----
| ("f" "video game" entry (file+olp+datetree
"~/org/videoGameImprovement.org")
| "* %<%Y-%m-%d %H:%M>\n** game notes
| *** %?
| ** video(s)
| *** video 1
| **** note 1 for video 1
| " :clock-in t)
`----
3 what happens
==============
I'm clocked into the place where `%?' takes me in the capture template
4 what I want to happen
=======================
I want to land at the first child of the `game notes' node but clock
into the `%<%Y-%m-%d %H:%M>' node 2 levels up
5 what I don't know how to do
=============================
5.1 In the capture template, I don't know how I could selectively use my
own implementation of `org-clock-in'
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5.1.1 Maybe I could have some sort of local binding surrounding just that
capture which would be used?
------------------------------------------------------------------------------------------------------
* 5.1.1.1 advice?
* 5.1.1.2 is an `add-hook' possible only within a certain scope?
Thanks,
Cody
[-- Attachment #2: Type: text/html, Size: 1710 bytes --]
next reply other threads:[~2018-07-14 4:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 4:59 Cody Goodman [this message]
2018-07-14 6:16 ` Override :clock-in (hence org-clock-in) behavior for a specific capture template Nicolas Goaziou
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=CADq_+R16-sDByJp0tRhOd-P2w-ZTU58BOjjs33wkLhsykwJqLA@mail.gmail.com \
--to=codygman.consulting@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).