From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Recording results of TODO items
Date: Wed, 16 Apr 2014 10:48:32 +0800 [thread overview]
Message-ID: <8761maf0qn.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CA+yBsdPbP74T60vzf3X2gTN2m1gOZHwSDa3OAzeFts7n4vUDRA@mail.gmail.com
William Kunkel <will@wkunkel.com> writes:
> I could well add it in a sub-heading under the TODO, I was just
> curious if there was a built-in org-mode way that I ought to be using
> instead of rolling something of my own.
Ah, no -- I think the state-change note is about as built-in as it gets...
> Cheers,
> Will
>
>
> On Tue, Apr 15, 2014 at 10:27 PM, Eric Abrahamsen <
> eric@ericabrahamsen.net> wrote:
>
> William Kunkel <will@wkunkel.com> writes:
>
> > Is there a standard way to record the outcomes of certain TODO
> items?
> > For example, I had a TODO item to research and come to a
> decision
> > about part of the architecture of a software project I'm
> starting,
> > and I'd like to record the result of that TODO item, that is,
> the
> > decision that I made. I found "closing notes" for TODO items,
> but
> > that's an option that applies to all TODO items and seems more
> > intended for brief remarks (to me, at least). Is using the
> closing
> > notes functionality my best bet, or is there something better?
> >
> > Thanks,
> > Will
>
> I do usually use the logging/notes functionality, but if you need
> more
> text, why not just make it the body of the TODO? A TODO is a
> heading
> like any other, you can just put a description of the outcome
> underneath
> it. If that gets unwieldy, separate the bits into multiple
> sub-headings,
> and/or make the TODO itself one smaller part of a larger TODO.
>
>
next prev parent reply other threads:[~2014-04-16 2:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 23:16 Recording results of TODO items William Kunkel
2014-04-16 2:27 ` Eric Abrahamsen
2014-04-16 2:29 ` William Kunkel
2014-04-16 2:48 ` Eric Abrahamsen [this message]
2014-04-16 2:48 ` William Kunkel
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=8761maf0qn.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).