From: Carsten Dominik <firstname.lastname@example.org>
To: John Wiegley <email@example.com>
Cc: emacs-orgmode Org-Mode <firstname.lastname@example.org>
Subject: Re: A much simpler way of handling dependent tasks
Date: Tue, 27 Jan 2009 08:43:23 +0100 [thread overview]
Message-ID: <641422A0-649D-450B-9AD7-AC136FCDB829@uva.nl> (raw)
I realize now that you do not make use of the code in
org-depend.el at all, which is what I thought at first.
- I can add the file, but then under a different name - org-depend
and org-depends are not different in the first 8 characters.
- I can move the code to org-agenda.el and create a variable to
turn this behavior on and off.
On Jan 27, 2009, at 8:31 AM, John Wiegley wrote:
> On Jan 27, 2009, at 2:47 AM, Carsten Dominik wrote:
>> Do you think it makes sense to integrate this code into org-
> Actually, I don't, since it's a completely different approach. org-
> depend.el as it stands now is based on a programmatic methodology,
> which more complex blocking schemes could be built on top of.
> I think this module represents something much simpler, which should
> be toggled by a single global boolean to indicate "on" or "off". My
> preference would be to see it mainlined, if that meets with your
> approval, Carsten.
next prev parent reply other threads:[~2009-01-27 7:43 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 [this message]
2009-01-27 22:51 ` Mike Newman
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).