From: "Michaël Parienti" <email@example.com>
Subject: Re: Scheduled date in closing note for repeated task
Date: Wed, 8 Jul 2009 07:39:47 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On Wed, 8 Jul 2009 07:10:20 +0200
Carsten Dominik <email@example.com> wrote:
> > I use a lot of repeated tasks, daily mostly, for which I want to log
> > the result as a note. So I use the "lognoterepeat" variable. But the
> > note doesn't contain the date of the task, just the date of when I
> > mark the task as done.
> > I would like to have:
> > ** TODO Did it rain this day?
> > SCHEDULED: <2009-07-06 Mon +1d>
> > - State "DONE" from "TODO" [2009-07-05 Sun] \\
> > No
> > - State "DONE" from "TODO" [2009-07-04 Sat] \\
> > Yes
> > Is there a way to have the desired result with an org variable?
> This is currently not possible. The date in the state change line
> is supposed to be the date when you acted, snd I would not think it
> is a good idea to change that.
Of course org-mode must not change its default behavior, but I was
thinking about an option that can be set by entry or by file.
> However, we might add a hook that
> can be used to pre-insert some stuff into the note buffer, and that
> hooks could
> be used to find and add the scheduled date.... Would that make sense?
A hook will be fine too. I will learn to use them :-)
gpg: D4C8 F73D A000 71C7 44EF 27E6 8982 4991 7126 3CE3
prev parent reply other threads:[~2009-07-08 5:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 15:33 Scheduled date in closing note for repeated task Michaël Parienti
2009-07-08 5:10 ` Carsten Dominik
2009-07-08 5:39 ` Michaël Parienti [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).