From: Carsten Dominik <dominik@science.uva.nl>
To: John Rakestraw <lists@johnrakestraw.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: checkboxes and agenda invisibility
Date: Thu, 19 Feb 2009 11:14:21 +0100 [thread overview]
Message-ID: <C3DBBBE6-6CD1-4C56-8032-A0F918435A01@uva.nl> (raw)
In-Reply-To: <20090201154424.2c07d9ff@johnrakestraw.com>
Hi John,
I agree with your reasoning and have implemented this.
Tasks that are blocked because of checkboxes will not be made
invisible, only dim.
- Carsten
On Feb 1, 2009, at 9:44 PM, John Rakestraw wrote:
> I noticed today that, at least in my set-up, setting these variables
> this way:
>
> (setq org-agenda-dim-blocked-tasks 'invisible)
> (setq org-enforce-todo-checkbox-dependencies t)
>
> means that a TODO task with checkboxes doesn't get included in the
> agenda. However, the sub-tasks in the checkbox list don't get
> included,
> either. So the TODO task with checkboxes doesn't show up in the
> agenda.
>
> It makes sense given the way the variables work. However, I wonder if
> it makes more sense for a task with checklisted sub-tasks to be
> included in the agenda so that the tasks and sub-tasks don't get lost.
> Or, to put the point slightly differently, I think that a TODO that's
> blocked because it has dependent TODOs might be treated differently in
> agenda listings than a TODO that's blocked because it has dependent
> checklist items.
>
> Not a big deal to me because I don't typically use checkboxes for TODO
> items. But I thought I'd raise it for consideration.
>
> --John
>
>
> _______________________________________________
> 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
prev parent reply other threads:[~2009-02-19 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 20:44 checkboxes and agenda invisibility John Rakestraw
2009-02-02 12:35 ` Carsten Dominik
2009-02-19 10:14 ` Carsten Dominik [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
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=C3DBBBE6-6CD1-4C56-8032-A0F918435A01@uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=lists@johnrakestraw.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).