From: Carsten Dominik <carsten.dominik@gmail.com>
To: Matthew Phillips <Matthew.Phillips@dsto.defence.gov.au>
Cc: emacs-orgmode@gnu.org
Subject: Re: Showing scheduled blocked tasks [SEC=UNCLASSIFIED]
Date: Mon, 15 Mar 2010 14:54:33 +0100 [thread overview]
Message-ID: <3902E439-068D-43D6-9B29-BC409CFD41C5@gmail.com> (raw)
In-Reply-To: <2E4514CA-FE52-4608-B0A7-B2D99C2C0591@dsto.defence.gov.au>
On Mar 15, 2010, at 1:23 AM, Matthew Phillips wrote:
> On 12/03/2010, at 3:29 AM, Carsten Dominik wrote:
>
> <snip>
>
>> On Mar 11, 2010, at 9:43 AM, Matthew Phillips wrote:
>>
>>> What I mean is setting it as an option in the custom commands does
>>> not seem to work, e.g. see list line in:
>>>
>>> (setq org-agenda-custom-commands
>>> ...
>>> ("d" "Daily Action List"
>>> ((agenda "" ((org-agenda-ndays 1)
>>> (org-agenda-sorting-strategy
>>> (quote ((agenda time-up priority-down tag-up) )))
>>> (org-deadline-warning-days 7)))
>>> (tags "TODO=\"STARTED\"+SCHEDULED=\"\"+DEADLINE=\"\""
>>> ((org-agenda-dim-blocked-tasks 'invisible)))
>>> ...
>>>
>>> The org-agenda-dim-blocked-tasks on the generated "tags" view does
>>> not get honoured. It *does* get honoured as a setting one level
>>> "higher", i.e. as a local setting to the whole org-agenda-custom-
>>> commands block, but that's not very useful here.
>>
>> OK, I see now what is happening here. The dimming of blocked tasks
>> is
>> done only once, at the very end, when the agenda has been made.
>> And that is outside the scope of the local options.
>>
>> You can use a normal (custom) agenda command and do the setting
>> there. Or you can use the global options for the block agenda to
>> set this for the entire block agenda. But not for a single segment
>> in a bloc agenda, I am afraid.
>>
>> Changing this would be significant work, and I don't want to do
>> this based on a single use case.
>
> OK, I can understand that.
>
> So, is there any way I can use a custom skip function in the TODO
> block to remove blocked tasks? Is there a way of getting the blocked
> status of a task from such a function?
Yes, BLOCKED is a virtual property which does this. I think you can
just do a tags/property/todo search like this
"-BLOCKED/+TODO"
Or you can test for the BLOCKED property in a user-written skip
function.
- Carsten
next prev parent reply other threads:[~2010-03-15 13:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 1:34 Showing scheduled blocked tasks [SEC=UNCLASSIFIED] Matthew Phillips
2010-03-11 6:10 ` Carsten Dominik
2010-03-11 8:43 ` Showing scheduled blocked tasks Matthew Phillips
2010-03-11 16:59 ` Carsten Dominik
2010-03-15 0:23 ` Showing scheduled blocked tasks [SEC=UNCLASSIFIED] Matthew Phillips
2010-03-15 13:54 ` Carsten Dominik [this message]
2010-03-16 0:36 ` Matthew Phillips
2010-03-16 7:51 ` Carsten Dominik
2010-03-17 0:53 ` Matthew Phillips
2010-03-18 5:59 ` Carsten Dominik
2010-03-22 4:41 ` Matthew Phillips
2010-03-15 16:26 ` Manish
2010-03-16 22:39 ` Matthew Phillips
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=3902E439-068D-43D6-9B29-BC409CFD41C5@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=Matthew.Phillips@dsto.defence.gov.au \
--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).