From: Carsten Dominik <carsten.dominik@gmail.com>
To: mrb@hsdev.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Combination of 'ordered' property and 'scheduled' hides TODO items.
Date: Sun, 4 Apr 2010 09:07:14 +0200 [thread overview]
Message-ID: <44C9772B-6C02-4750-8292-3C610D81720B@gmail.com> (raw)
In-Reply-To: <20100331110504.7f161bb9@hsdev.com>
Hi,
you would have to write your own functions for the blocker hook and
install it instead of the default one. If would not be so hard -
basically call the default blocker hook function and then test
yourself if the entry is scheduled, and combine the result.
However, I would just use a normal agenda, where you set org-agenda-
dim-blocked-tasks to nil in the option section.
HTH
- Carsten
On Mar 31, 2010, at 11:05 AM, mrb@hsdev.com wrote:
> Hi,
>
> I'm using the ORDERED property in some/most of my projects and
> generally hide BLOCKED items everywhere except in a special list of
> blocked items which I review with some regularity. Overall, this works
> fine, org nicely filters out what is possible to work on and hides
> others.
>
> I'd like to make it a bit smarter by having scheduled and deadlined
> items be 'unhidden' even though they would be invisible according to
> their order.
>
> A typical structure to which the above would apply is something like
> this:
>
> * PROJ Some project with sequential tasks
> :PROPERTIES:
> :ORDERED: t
> :END:
> ** TODO First
> ** TODO Second, but scheduled
> SCHEDULED: <2010-03-30 Tue>
> ** TODO Third, but deadlined
> DEADLINE: <2010-03-29 Mon>
> ** TODO Last
>
> In my lists the 'Second, but scheduled' and 'Third, but deadlined' do
> not appear, because they are blocked by 'First'.
>
> For the above situations, I'd like to make an exception in the hiding,
> but do not know where to start. I could imagine a customization
> variable which allows a list of exceptions to the 'hide' rule.
>
> Anyone has any tips/pointers on the above?
>
> Thx,
> marcel
>
> --
> Marcel van der Boom -- http://hsdev.com/mvdb.vcf
> HS-Development BV -- http://www.hsdev.com
> So! web applications -- http://make-it-so.info
> Cobra build -- http://cobra.mrblog.nl
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
- Carsten
next prev parent reply other threads:[~2010-04-04 7:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 9:05 Combination of 'ordered' property and 'scheduled' hides TODO items mrb
2010-04-04 7:07 ` Carsten Dominik [this message]
2010-04-04 7:42 ` mrb
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=44C9772B-6C02-4750-8292-3C610D81720B@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mrb@hsdev.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).