From: Olaf Meeuwissen <olaf.meeuwissen@avasys.jp>
To: John J Foerch <jjfoerch@earthlink.net>
Cc: emacs-orgmode@gnu.org
Subject: Storing log notes at capture (was Re: feature request for org-store-log-note)
Date: Wed, 05 Oct 2011 09:15:07 +0900 [thread overview]
Message-ID: <87d3eccn04.fsf@avasys.jp> (raw)
In-Reply-To: <8762kdcwvk.fsf@hecubus.retroj.net> (John J. Foerch's message of "Tue, 27 Sep 2011 20:51:27 -0400")
John J Foerch <jjfoerch@earthlink.net> writes:
> I use org to manage TODO lists in which I want to keep time stamps for
> the creation of an item, and for each state change. To be as clear as
> possible, I'll just paste the portion of my config that affects how
> TODOs work:
>
> (setq org-treat-insert-todo-heading-as-state-change t
> org-log-into-drawer t
> org-log-done nil)
> ;;; [snip]
>
> (setcdr (assq 'state org-log-note-headings)
> "State -> %s %t")
>
> This logs each state change (including creation) into the LOGBOOK
> drawer. It's great.
I thought so too. I'd like to record creation in the logbook drawer
when I capture a TODO and have adjusted my templates to do so. They
just include the logbook drawer literally, like so
"* TODO %?
:LOGBOOK:
- State \"TODO\" from \"\" %U
:END:
%a
%i"
I thought that org-treat-insert-todo-heading-as-state-change would be
able to create the drawer for me but no such luck. Duh, capturing is
not a state change now is it.
Anyway, is there a smarter way to log creation at capture?
Thanks in advance,
--
Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962 Help support software freedom
http://www.fsf.org/jf?referrer=1962
prev parent reply other threads:[~2011-10-05 0:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 0:51 feature request for org-store-log-note John J Foerch
2011-09-28 2:28 ` Juan Pechiar
2011-09-28 3:45 ` John J Foerch
2011-10-05 0:15 ` Olaf Meeuwissen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d3eccn04.fsf@avasys.jp \
--to=olaf.meeuwissen@avasys.jp \
--cc=emacs-orgmode@gnu.org \
--cc=jjfoerch@earthlink.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.