From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Eddward DeVilla" <eddward@gmail.com>
Subject: Re: Re: Org-mode 4.69
Date: Wed, 21 Mar 2007 10:18:56 -0500
Message-ID: <b71b18520703210818o3a1e1745y502265d8ec615dd7@mail.gmail.com>
References: <c415d6115e762715c6607c2be6cbc97e@science.uva.nl>
	<m24poehp6t.fsf@sl392.st-edmunds.cam.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HU2cK-0002IX-Uw
	for emacs-orgmode@gnu.org; Wed, 21 Mar 2007 11:20:49 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HU2cH-0002AN-Ui
	for emacs-orgmode@gnu.org; Wed, 21 Mar 2007 11:20:48 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HU2cH-0002A6-MK
	for emacs-orgmode@gnu.org; Wed, 21 Mar 2007 10:20:45 -0500
Received: from nf-out-0910.google.com ([64.233.182.190])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <eddward@gmail.com>) id 1HU2aZ-0005Rs-Qi
	for emacs-orgmode@gnu.org; Wed, 21 Mar 2007 11:19:00 -0400
Received: by nf-out-0910.google.com with SMTP id m18so891899nfc
	for <emacs-orgmode@gnu.org>; Wed, 21 Mar 2007 08:18:57 -0700 (PDT)
In-Reply-To: <m24poehp6t.fsf@sl392.st-edmunds.cam.ac.uk>
Content-Disposition: inline
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: Leo <sdl.web@gmail.com>
Cc: emacs-orgmode@gnu.org

On 3/21/07, Leo <sdl.web@gmail.com> wrote:
> On 2007-03-21, Carsten Dominik said:
>
> >   - You can now use multiple sets of TODO keywords in the same
> >     buffer.  For example, you may put the following three lines
> >     into a file:
> >
> >       #+SEQ_TODO: TODO DONE
> >       #+SEQ_TODO: REPORT BUG KNOWNCAUSE RESOLVED
> >       #+TYP_TODO: Fred Laura Peter Me OK
>
> I feel this too complicated. Isn't it more intuitive and consistent to
> make this work like #+CATEGORY and #+ARCHIVE?

You meaning having one sequence going at a time and replacing it with
each use of #+SEQ_TODO: or  #+TYP_TODO:?  I don't think I'd like that,
but I could see how other might use it and how having multiple
sequences at once could polute the names space so to speak.

How about a generalize syntax where you name a sequence.  If you don't
give a name you are defining/replacing the null or default sequnce.
So:

===============================================
#+SEQ_TODO: TODO DONE
#+SEQ_TODO: (BUG-TRACKING) REPORT BUG KNOWNCAUSE RESOLVED
#+TYP_TODO: (TEAM) Fred Laura Peter Me OK
.
.
.
#+SEQ_TODO: TODO WORKING DONE
Now the default is redefined
.
.
.
#+TYP_TODO: (TEAM)
The TEAM todo type is effectively gone.
===============================================

This would let me have my set of TODO 'types'.  It would allow others
to redifne the default todo sequence without having them all at once.
It might be a pita to implement though.

Edd