|
From: | Carsten Dominik |
Subject: | Re: [Orgmode] More Flexibility for Stuck Projects? |
Date: | Thu, 19 Mar 2009 17:40:34 +0100 |
Hi Peter, I guess you might want to use (setq org-tags-exclude-from-inheritance '("project" "subproject")) Then you can select projects for the stuck-project listing with "project|subproject" If you have a reason to actually want the inheritance of these tags in other circumstances, you could implement this setting as an option to an agenda custom command that does look for stuck projects: (("#" "Stuck" stuck "" ((org-tags-exclude-from-inheritance '("project" "subproject")))) To answer to your original question: On Mar 18, 2009, at 6:01 PM, Peter Jones wrote:
"+project+LEVEL=2|+subproject+LEVEL=3"
I am using TODO keywords #+TODO: PROJ | PRDONE PRCANCELLED to make projects, because they do not involve inheritance, and a project is never a TODO item itself, only the subtasks are.... Now, maybe the real problem you are having is this: When the stuck project search goes through your tree, it first finds a project tree and checks if it is stuck. If not, the entire tree is skipped, including the subprojects. This is not what you want. The best solution probably is to say that a project that has sub projects is never stuck, by adding the subproject tag to the unstuck conditions. Hmm, I see now that part of this problem stems from the fact that the skipper skips the entire subtree and never looks at subitems. Maybe this is a mistake... I actually think it is. I am changing this... done. With this change, I guess you can switch to - use :project: to define both projects and subprojects - exclude :project: from inheritance - define your stuck project search "+project" to identify a project. or - use a TODO keyword PROJ - define the search as "TODO=\"PROJ\"" HTH - Carsten
|
[Prev in Thread] | Current Thread | [Next in Thread] |