emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: John Hendy <jw.hendy@gmail.com>
To: nicholas.dokos@hp.com
Cc: Angel de Vicente <angelv@iac.es>, emacs-orgmode@gnu.org
Subject: Re: automatically mark DONE when all sub checkboxes are checked
Date: Fri, 10 Feb 2012 20:20:49 -0600	[thread overview]
Message-ID: <CA+M2ft_nLXcUEKWPcGDv5+ThCJrXr=KM1JYWwg3XjXEqJRQvjQ@mail.gmail.com> (raw)
In-Reply-To: <8332.1328920874@alphaville>

On Fri, Feb 10, 2012 at 6:41 PM, Nick Dokos <nicholas.dokos@hp.com> wrote:
> John Hendy <jw.hendy@gmail.com> wrote:
>
>> ,---
>> | Note that the code requires that a checkbox statistics
>> | cookie be present in order for it to work.
>> `---
>>
>> I had no idea what that meant and thought it was just reiterating that
>> you actually need checkboxes for this to work. Now it makes sense.
>> Even inserting "(a statistics cookie is [/] or [%] in the parent todo
>> headline)" would make it crystal clear.
>>
>
> The manual refers to them as "cookies": searching the index for either
> "statistics" or "cookie" takes you to section 5.6 where they are
> described.

Alright, alright... I should have rt[f]m :)

>
> But you should feel free to add the appropriate words: Worg (as you
> know) is editable, and if you found it confusing, somebody else will too
> (nudge, nudge). But I beat you to it in this case: thanks for the
> suggestion and also for noticing the extra paren as well. OTOH, if you
> don't like my verbiage, feel free to change it!
>

I will do this :)

> BTW, I don't agree that this should be default behavior (as Angel, I
> believe, suggested): whether an item is done may be a matter of checking
> boxes in some cases, but not always - for myself, I would like to
> maintain the ultimate authority of declaring something done and not to
> relegate it to mere code (is that provocative enough? :-) )
>
> In addition, the function slows things down (every time you
> check a box, the function runs), it makes a few assumptions about the
> environment (todo states, statistics cookies), and I certainly would not
> trust it to DTRT all the time: it would need hardening.
>

I don't use it, so I don't really care, but I get what you're saying.
I think it should be opt-in. A todo might have *some* things that
you'd like to keep track of with checkboxes, but the task as a whole
might have some other requirement and thus shouldn't really be done
until the user decides.

I'll add a link in the FAQ pointed at the manual section about those
this weekend.


Thanks,
John

> Nick
>

next prev parent reply	other threads:[~2012-02-11  2:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 21:06 automatically mark DONE when all sub checkboxes are checked Peter Salazar
2012-02-10 21:13 ` John Hendy
2012-02-10 22:31   ` Angel de Vicente
2012-02-10 22:47     ` John Hendy
2012-02-11  0:41       ` Nick Dokos
2012-02-11  2:20         ` John Hendy [this message]
2012-02-11 18:17 ` Nick Dokos
2012-02-13  8:08   ` Peter Salazar

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='CA+M2ft_nLXcUEKWPcGDv5+ThCJrXr=KM1JYWwg3XjXEqJRQvjQ@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=angelv@iac.es \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.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

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).