From: "Eddward DeVilla" <eddward@gmail.com>
To: Leo <sdl.web@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Org-mode 4.69
Date: Wed, 21 Mar 2007 10:18:56 -0500 [thread overview]
Message-ID: <b71b18520703210818o3a1e1745y502265d8ec615dd7@mail.gmail.com> (raw)
In-Reply-To: <m24poehp6t.fsf@sl392.st-edmunds.cam.ac.uk>
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
prev parent reply other threads:[~2007-03-21 15:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 9:00 Org-mode 4.69 Carsten Dominik
2007-03-21 10:21 ` Leo
2007-03-21 10:36 ` Carsten Dominik
2007-03-21 14:27 ` Jason F. McBrayer
2007-03-21 15:11 ` Carsten Dominik
2007-03-21 22:21 ` Carsten Dominik
2007-03-21 23:28 ` Jason F. McBrayer
2007-03-22 13:59 ` Carsten Dominik
2007-03-22 15:21 ` Jason F. McBrayer
2007-03-22 15:50 ` Carsten Dominik
2007-03-22 16:45 ` Jason F. McBrayer
2007-03-26 16:29 ` Carsten Dominik
2007-03-21 15:07 ` Eddward DeVilla
2007-03-21 15:18 ` Eddward DeVilla [this message]
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=b71b18520703210818o3a1e1745y502265d8ec615dd7@mail.gmail.com \
--to=eddward@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sdl.web@gmail.com \
/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).