From: Ulf Stegemann <ulf-news@zeitform.de>
To: emacs-orgmode@gnu.org
Subject: Re: Counter cookies and mixed checkbox lists/subtasks
Date: Thu, 16 Apr 2009 11:05:19 +0200 [thread overview]
Message-ID: <zf.upnd4bdj7e8.fsf@zeitform.de> (raw)
In-Reply-To: 7F5AF424-5413-44D5-A73C-A4BA6B9FB5F9@gmail.com
Hi Carsten,
Carsten Dominik <carsten.dominik@gmail.com> wrote:
> there is no way currently to force a cookie either way.
>
> I think the the right solution is to modify the structure, so
> that the check boxes are only in entries without children.
> Seems to me that this is always possible - in your case
> you could just create a "first child" that gets the checkboxes.
okay, as said, this is rather a minor annoyance. However, fixing this
might nevertheless be desirable since the combination of checkboxes and
todo item is quite powerful.
Imagine you are compiling a document where you need contributions from
others. You could make a todo item for this with checkboxes for every
chapter planned (or for every author you expect input from, or ...). As
soon as contributions from authors arrive, you create todo items
preferably below the same initial todo item, indicating that you have to
integrate input. When compiling the document you finish those todo items
on the one hand and on the other hand checkboxes will eventually get
checked as chapters are finished. Although putting the chapter
checkboxes into its own sub-item is possible, much of the simplicity and
elegance of the original approach gets lost. What do you think?
Ulf
next prev parent reply other threads:[~2009-04-16 9:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 8:40 Counter cookies and mixed checkbox lists/subtasks Ulf Stegemann
2009-04-08 14:47 ` Carsten Dominik
2009-04-16 9:05 ` Ulf Stegemann [this message]
2009-04-16 11:45 ` Carsten Dominik
2009-04-16 13:24 ` Ulf Stegemann
2009-04-17 16:50 ` Carsten Dominik
2009-04-20 8:00 ` Ulf Stegemann
2009-04-22 4:16 ` Carsten Dominik
2009-04-22 8:08 ` Ulf Stegemann
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=zf.upnd4bdj7e8.fsf@zeitform.de \
--to=ulf-news@zeitform.de \
--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).