From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rick Moynihan Subject: Re: org-mode & multiple TODO sequences within a file. Date: Mon, 19 Mar 2007 12:47:38 +0000 Message-ID: <45FE866A.1050002@calicojack.co.uk> References: <45F9783C.8050801@calicojack.co.uk> <1b5202b10a64cf5f04b443c331014035@science.uva.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HTHIM-0007ZC-0w for emacs-orgmode@gnu.org; Mon, 19 Mar 2007 08:49:02 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HTHIJ-0007Ye-TN for emacs-orgmode@gnu.org; Mon, 19 Mar 2007 08:49:01 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HTHIJ-0007Yb-Mq for emacs-orgmode@gnu.org; Mon, 19 Mar 2007 07:48:59 -0500 Received: from storm.bpweb.net ([83.223.106.8]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1HTHGr-0005z0-7a for emacs-orgmode@gnu.org; Mon, 19 Mar 2007 08:47:29 -0400 In-Reply-To: <1b5202b10a64cf5f04b443c331014035@science.uva.nl> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: emacs-orgmode@gnu.org 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.