From: John Wiegley <johnw@newartisans.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode Org-Mode <emacs-orgmode@gnu.org>,
Rainer Stengele <rainer.stengele@diplan.de>
Subject: Re: A much simpler way of handling dependent tasks
Date: Fri, 30 Jan 2009 16:07:20 -0400 [thread overview]
Message-ID: <1DC80FBD-4668-4796-A150-643BDB7D7EAE@newartisans.com> (raw)
In-Reply-To: <3F4D68F7-625A-472C-9D89-8D6766D61C76@uva.nl>
On Jan 30, 2009, at 1:37 PM, Carsten Dominik wrote:
> So my feeling is that switching from one not-done state to
> another not-done state should not be blocked at all.
> In fact, I feel the same for the straight TODO dependencies.
>
> I have now adapted John's mechanism in the following way:
>
> - You are free to change between the different non-done states
>
> - Entries that cannot be switched to DONE will be greyed in
> the agenda, but you can still use the agenda to switch them
> between not-done states.
>
> - If you call `C-c C-t' (or `t' in the agenda) with a
> tripple C-u prefix, any blocking will be circumvented
> for the upcoming state change. This is good if you
> want to cancel such a tree, before all subitems are done.
>
> I think this is good, and I hope that John agrees.
Very much so, that's a great extension. I use checkboxes like Rainer
does constantly, for "lightweight dependent" tasks. I'll make use of
this extension a great deal.
John
prev parent reply other threads:[~2009-01-30 20:07 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
2009-01-30 15:02 ` Rainer Stengele
2009-01-30 17:37 ` Carsten Dominik
2009-01-30 20:07 ` John Wiegley [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1DC80FBD-4668-4796-A150-643BDB7D7EAE@newartisans.com \
--to=johnw@newartisans.com \
--cc=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=rainer.stengele@diplan.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.