From: Bernt Hansen <bernt@norang.ca>
To: Mark Scala <markscala@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: capture question
Date: Thu, 11 Aug 2011 19:32:21 -0400 [thread overview]
Message-ID: <87mxff34oq.fsf@norang.ca> (raw)
In-Reply-To: <CAFTGpA9fVK=yZdKbmTUco7sX7pAvhf9A5yLOmjTDSnJJZs44NA@mail.gmail.com> (Mark Scala's message of "Thu, 11 Aug 2011 11:52:06 -0500")
Mark Scala <markscala@gmail.com> writes:
> Hi,
>
> I've been using capture for, among other things, capturing
> interruptions to clocked tasks. For this, I use something like the
> following template:
>
> ("i" "interruption" entry (file "refile.org") "A TEMPLATE HERE"
> :clock-in t :clock-resume t)
>
> One thing that has been bothering me is that there are really two
> types of interruption that deserve different treatment. Sometimes
> the interrupting task is completed by the time I file it with C-c
> C-c. Other times it is not. But both types are filed with the todo
> keyword STARTED. For those (and only those) interruptions that are
> finished by the time I file them, I'd like them to have the keyword
> DONE automatically. Has anyone encountered this case and found a
> solution?
Hi Mark,
Just add one step to mark the task DONE before you file it away.
C-c C-t d (mark DONE)
C-c C-c (file it and stop the clock)
How is org-mode supposed to divine that this task you are capturing is
DONE when you file it but another one isn't? You'll have to indicate
somehow how you differentiate between these capture tasks.
If you can do that programmatically maybe you can add a capture hook
which marks the task done when you file it.
Regards,
Bernt
next prev parent reply other threads:[~2011-08-11 23:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 16:52 capture question Mark Scala
2011-08-11 23:32 ` Bernt Hansen [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-02 8:30 Capture Question Robert Inder
2011-02-25 0:02 Capture question John Hendy
2011-03-06 13:19 ` Bastien
2011-03-06 16:16 ` John Hendy
2011-03-06 17:24 ` Bastien
2011-03-06 18:12 ` John Hendy
2011-03-06 19:47 ` suvayu ali
2011-03-06 20:06 ` John Hendy
2011-03-06 20:33 ` Suvayu Ali
2011-03-19 14:41 ` Matt Lundin
2011-03-19 14:46 ` Suvayu Ali
2011-03-07 8:24 ` Bastien
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=87mxff34oq.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=markscala@gmail.com \
/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).