emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Stuart McLean" <makhector@gmail.com>
To: emacs-orgmode@gnu.org
Subject: TODO dependencies
Date: Fri, 25 Jan 2008 07:45:10 -0800	[thread overview]
Message-ID: <a3de0c990801250745w4a5935f8wbe3338ba3f80f641@mail.gmail.com> (raw)

Hi,

Sorry if I have started a new thread on this subject, GMail and I are
not getting along right now.

** TODO a main project
*** TODO step 1
*** TODO step 2
*** TODO step 3
**** TODO step 3 part a
**** TODO step 3 part b
**** TODO step 3 part c
and so on
*** TODO step 4

Here is the functionality that I would like, and (as I see it) that
would be possible with the hooks provided and extensions that the user
could write...

marking ** TODO a main project
as DONE would mark all subheadings done (say you did them all at once)

marking *** TODO step 1
as DONE would mark this item as done and no more, and so on for step two.

marking step three as DONE would mark step three and all children (a,
b, c) as done, again, say you did them all at once. However, if you
marked step 3, part a as DONE, then b (at a later time), then c, only
triggering "c" would mark *** TODO step 3 as DONE as well.

In other words marking a heading as DONE will mark all children as
DONE, marking children as DONE one-by-one will only mark the parent as
DONE when all the children are marked DONE.

Is this a correct understanding?

This is (one of the functionalities) I would like. Maybe it is already
possible, or I have misread something?

Thanks again for org-mode, *fantastic software*

Stuart

             reply	other threads:[~2008-01-25 15:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-25 15:45 Stuart McLean [this message]
2008-01-25 16:11 ` TODO dependencies Hugo Schmitt
  -- strict thread matches above, loose matches on Subject: below --
2007-10-19  6:27 Carsten Dominik
2007-10-19  6:35 ` Rainer Stengele
2008-01-21 14:43 ` Carsten Dominik
2008-01-21 17:43   ` Adam Spiers
2008-01-21 19:10     ` Carsten Dominik

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=a3de0c990801250745w4a5935f8wbe3338ba3f80f641@mail.gmail.com \
    --to=makhector@gmail.com \
    --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).