Re: org-mode & multiple TODO sequences within a file.

[Rick Moynihan <rick@calicojack.co.uk>]

Bastien wrote:
> Rick Moynihan <rick@calicojack.co.uk> writes:
> 
>> I can see that my suggestion would add complexity in both code and org
>> files.  Supporting multiple DONE states would be a nice, especially if
>> they integrate properly with the agenda.
> 
> Maybe we could use the same grouping conventions than for tags :
> 
>   #+SEQ_TODO: TODO NEXT INPROGRESS WAITING { ACHIEVED DONE }
> 
> That would make it easy to have several states and just a few logging
> steps.  Consider the next sequence being just *three* states :
> 
>   #+SEQ_TODO: { TODO NEXT } { INPROGRESS WAITING } { ACHIEVED DONE }
>               `-> state 1   |                      |
>                             `-> log-state 2        |
>                                                    `-> state 3    
> 

I quite like the idea of grouping the sequences within braces.  However, 
I think we might be describing (slightly) different things.  To clarify 
what I'd REALLY like to be able to do is to define different sequences, 
for use within a single file, rather than a single sequence made up of 
sub-sequences.

a hypothetical example:

#+SEQ_TODO: { TODO DONE } { BUG RESOLVED } { REQUIREMENTS DESIGN 
DEVELOPMENT TESTING }

This would define 3 sequences which are each for different things, and 
might even be unrelated, though nesting related sequences might be quite 
nice:

* TESTING

** BUG

   Bug report...

*** TODO Identify cause

   Suspect foo is the problem.


Here I've assumed that the last state within each group is the final 
DONE state, though it might also be pretty neat if multiple DONE states 
could be supported.

Anyway, it's just an idea.

Thanks again,

R.