From: Rick Moynihan <rick@calicojack.co.uk>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode & multiple TODO sequences within a file.
Date: Mon, 19 Mar 2007 12:47:38 +0000 [thread overview]
Message-ID: <45FE866A.1050002@calicojack.co.uk> (raw)
In-Reply-To: <1b5202b10a64cf5f04b443c331014035@science.uva.nl>
Carsten Dominik wrote:
> No, this does not work. Could be done, of course, but adds complexity,
> and I am sure once it is there, people will want to switch
> TODO keywords constantly, filling the entire file with new #+TODO
> statements. Does not feel right.
>
> How about the following alternative:
>
> Just make a long sequence containing all the subsequences,
> like
>
> #+SEQ_TODO: REPORT BUG KNOWNCAUSE RESOLVED TODO WAITING VERIFY DONE
>
> You can then use command like `M-5 C-c C-t'
> (or `5 t' in the agenda) to jump to
> TODO in this sequence. Basically, you need to remember where
> in your list the different sequences start, put items onto
> the right starting point, and then work through your states.
>
> Hmmm, looking at this it might actually be useful to
> allow additional DONE states in the middle of the sequence, but
> this will at least currently lead to problems, both when cycling
> from DONE to nothing to TODO, and also in the highlighting
> of TODO keywords in the agenda. I'll check if I can fix these
> small issues.
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.
R.
next prev parent reply other threads:[~2007-03-19 12:49 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 [this message]
2007-03-19 16:25 ` Bastien
2007-03-19 18:06 ` Rick Moynihan
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=45FE866A.1050002@calicojack.co.uk \
--to=rick@calicojack.co.uk \
--cc=dominik@science.uva.nl \
--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).