Alright, I'll just do my own thing then, I suppose. Thanks! On Tue, Apr 15, 2014 at 10:48 PM, Eric Abrahamsen <e...@ericabrahamsen.net>wrote:
> William Kunkel <w...@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 < > > e...@ericabrahamsen.net> wrote: > > > > William Kunkel <w...@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. > > > > > > >
