emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: "Jason F. McBrayer" <jmcbray@carcosa.net>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Re: Org-mode 4.69
Date: Thu, 22 Mar 2007 14:59:25 +0100	[thread overview]
Message-ID: <b3a2d35b6a503f8fbf510c4fdc67dcd4@science.uva.nl> (raw)
In-Reply-To: <1174519698.12401.13.camel@bertrand.carcosa.net>


On Mar 22, 2007, at 0:28, Jason F. McBrayer wrote:

> 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
>
> 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.

Thank you very much, but this is a bit tricky, so maybe I should do 
this.
If you send me a complex patch, we need to get your papers with the FSF
first, or I cannot install the fixes into Emacs.  I already have the 
papers
from David and Piotr, so if you plan to contribute code in the future, 
maybe
we should go ahead and do this.

>
>> 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.

There is one difference.  When everything is in one line, I'd expect
C-c C-t to reach these states.  When they are in different lines,
you will need C-S-right to get to them.  Both ways have their
advantages.  I guess for a special state like CANCELED, a separate
sequence would be good, but I can imagine cases where one would
like different ways of saying an entry is done.

- Carsten

  reply	other threads:[~2007-03-22 14:01 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 [this message]
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=b3a2d35b6a503f8fbf510c4fdc67dcd4@science.uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=jmcbray@carcosa.net \
    /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).