emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Jason F. McBrayer" <jmcbray@carcosa.net>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Re: Org-mode 4.69
Date: Wed, 21 Mar 2007 19:28:18 -0400	[thread overview]
Message-ID: <1174519698.12401.13.camel@bertrand.carcosa.net> (raw)
In-Reply-To: <1a5d239e5dac5e568bbbd7187b125efa@science.uva.nl>

On Wed, 2007-03-21 at 23:21 +0100, Carsten Dominik wrote:

> > On Mar 21, 2007, at 15:27, Jason F. McBrayer wrote:
> >
> >> Carsten Dominik <dominik@science.uva.nl> writes:

> >> All I really need it for is multiple DONE states (e.g. COMPLETED
> >> vs. CANCELLED).  The current implementation works okay for that,
> >> though it's somewhat overkill.
> >
> > Not so bad, maybe:
> >
> > #+SEQ_TODO: TODO DONE
> > #+SEQ_TODO: RESOLVED
> > #+SEQ_TODO: CANCELLED

This is, in fact, more or less what I'm doing.  Actually I have one
sequence for actions, one for projects, and one for unusual states (like
CANCELLED);  I'm finding more uses for it as time goes on.   So the
extra flexibility is more than I actually need, but not so much that I
can't see any use for it.

I would like to see this settable in lisp, though, since I want to use
my TODO keywords all across my GTD system rather than different ones in
different files.  I can probably try to put together a patch to do this
tomorrow, just so that I'm not kibitzing without offering code.

> Or maybe this should actually be like this:?
> 
> #+SEQ_TODO: TODO | DONE RESOLVED CANCELLED

I don't think an extra syntax would be too worthwhile.  If you're
already setting TODO keywords in the file itself, three lines vs. one
line is not a big deal.

-- 
+-----------------------------------------------------------+
| Jason F. McBrayer                    jmcbray@carcosa.net  |
| If someone conquers a thousand times a thousand others in |
| battle, and someone else conquers himself, the latter one |
| is the greatest of all conquerors.  --- The Dhammapada    |

  reply	other threads:[~2007-03-21 23:30 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 [this message]
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

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=1174519698.12401.13.camel@bertrand.carcosa.net \
    --to=jmcbray@carcosa.net \
    --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).