emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rick Moynihan <rick@calicojack.co.uk>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode & multiple TODO sequences within a file.
Date: Mon, 19 Mar 2007 18:06:21 +0000	[thread overview]
Message-ID: <45FED11D.2020600@calicojack.co.uk> (raw)
In-Reply-To: <87bqipp5dw.fsf@bzg.ath.cx>

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.

  reply	other threads:[~2007-03-19 18:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-15 16:45 org-mode & multiple TODO sequences within a file Rick Moynihan
2007-03-18 20:11 ` Carsten Dominik
2007-03-19 12:47   ` Rick Moynihan
2007-03-19 16:25     ` Bastien
2007-03-19 18:06       ` Rick Moynihan [this message]
2007-03-20 16:01         ` Bastien

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=45FED11D.2020600@calicojack.co.uk \
    --to=rick@calicojack.co.uk \
    --cc=bzg@altern.org \
    --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).