From: Mike Newman <firstname.lastname@example.org>
Subject: Re: A much simpler way of handling dependent tasks
Date: Tue, 27 Jan 2009 22:51:23 +0000 [thread overview]
Message-ID: <email@example.com> (raw)
On Mon, 26 Jan 2009 17:16:17 -0400
John Wiegley <firstname.lastname@example.org> wrote:
> I've been wanting a simple method for managing dependent tasks for
> some time now, and only now did it occur to me that I could just
> implement a much simpler method using your current blocking mechanism.
> The attached file, confusingly named org-depends.el, implements the
> following scheme:
> 1. Any TODO which has incomplete child TODOs is blocked.
> 2. If a parent TODO has the ORDERED property, it's children must be
> completed in order. Undone siblings block later siblings.
> 3. Blocked items are greyed out in the agenda list.
This sounds like a sensible approach that would cover most my needs for
dependencies between TODOs
next prev parent reply other threads:[~2009-01-27 22:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 21:16 A much simpler way of handling dependent tasks John Wiegley
2009-01-26 23:48 ` Oliver Charles
2009-01-27 1:18 ` Jesse Alama
2009-01-27 6:46 ` Carsten Dominik
2009-01-27 6:47 ` John Wiegley
2009-01-27 6:47 ` Carsten Dominik
2009-01-27 7:31 ` John Wiegley
2009-01-27 7:43 ` Carsten Dominik
2009-01-27 22:51 ` Mike Newman [this message]
2009-01-30 15:02 ` Rainer Stengele
2009-01-30 17:37 ` Carsten Dominik
2009-01-30 20:07 ` John Wiegley
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).