emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Hugo Schmitt" <hugows@gmail.com>
To: Stuart McLean <makhector@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: TODO dependencies
Date: Fri, 25 Jan 2008 13:11:26 -0300	[thread overview]
Message-ID: <2f1c7d020801250811i7d5a52f9p6bafc4f55d5b47ba@mail.gmail.com> (raw)
In-Reply-To: <a3de0c990801250745w4a5935f8wbe3338ba3f80f641@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1736 bytes --]

And the parent could also support the [%] notation that exists for
checkboxes :)

-Hugo

On Jan 25, 2008 12:45 PM, Stuart McLean <makhector@gmail.com> wrote:

> 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
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>

[-- Attachment #1.2: Type: text/html, Size: 2183 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2008-01-25 16:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-25 15:45 TODO dependencies Stuart McLean
2008-01-25 16:11 ` Hugo Schmitt [this message]
  -- 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=2f1c7d020801250811i7d5a52f9p6bafc4f55d5b47ba@mail.gmail.com \
    --to=hugows@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=makhector@gmail.com \
    /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).