Carsten Dominik writes:
> On May 17, 2010, at 2:14 PM, Bernt Hansen wrote:
>
>> Carsten Dominik writes:
>>
>>> In the stuck project definition, adding "^\\*\\{3,\\}" as the 4th
>>> element should exclude anything that has level 3 or up in the
>>> subtree.
>>
>> I don't think this will work. The
On May 17, 2010, at 2:14 PM, Bernt Hansen wrote:
Carsten Dominik writes:
In the stuck project definition, adding "^\\*\\{3,\\}" as the 4th
element should exclude anything that has level 3 or up in the
subtree.
I don't think this will work. The regexp matches all tasks with
level 3
or
Carsten Dominik writes:
> In the stuck project definition, adding "^\\*\\{3,\\}" as the 4th
> element should exclude anything that has level 3 or up in the subtree.
I don't think this will work. The regexp matches all tasks with level 3
or higher subtrees ... which is all projects so all projec
This works:
("p" "Projects" tags-todo "LEVEL=2/!-DONE-CANCELLED"
((org-agenda-skip-function
'(org-agenda-skip-subtree-if 'notregexp "^\\*\\{3,\\}"
("o" "Other (non-project tasks)" tags "LEVEL=2/!-DONE-CANCELLED"
((org-agenda-skip-function
'(org-agenda-skip-subtree-if 'regexp "^\\
Hi Bernt,
I guess you can use the regexp options, both in the stuck projects,
and in a skipping condition for an agenda custom command.
In the stuck project definition, adding "^\\*\\{3,\\}" as the 4th
element should exclude anything that has level 3 or up in the subtree.
for the agenda c
