Re: "clearing" the state of an org-mode subtree

[Bernt Hansen <bernt@norang.ca>]

Paul Mead <paul.d.mead@gmail.com> writes:

> Robert Goldman <rpgoldman@sift.info> writes:
>
>> Andrew Stribblehill wrote:
>>> org-mode files are plain text. M-% to do a replacement: once you've
>>> entered your search term and its replacement, hit ! to replace all
>>> without question.
>>
>> Yes, one can do this, but note that it's not entirely a no-brainer.  You
>> need to:
>>
>> 1.  clear all the check boxes and then recompute all checkbox counts in
>> the region.  [this isn't a simple tag replacement]
>>
>> 2.  replace all non-TODO keywords with TODO.  This is a replacement, but
>> not a simple one to do with M-%
>>
>> 3.  Wipe out all of the notes that were added with state changes.
>> Again, this can be done with a replacement command, but it's not a
>> trivial one.
>>
>> This is one of those cases where automating a task will not pay back the
>> investment (at least not to me, individually), so I think I'd better
>> just do it by hand.
>>
>> Thanks, everyone,
>
> Have you thought about using yasnippet? I have a repeating set of TODOs
> in a particular order that I have to do every month. Rather than reusing
> the old structure, I just insert it again from a snippet. That way I
> also have all my notes from last month too.

Or copy the subtree _before_ you fill it in with details.  Make a
repeating task that is just to copy the subtree at the appropriate time
so the subtree is available for the repeat after this one, and then
proceed to use one of the copies for the current task iteration.

HTH,
Bernt