clarification about org-mode

clarification about org-mode

[Richard G Riley]

The spate of design memos about GUIDs and scheduling leads me to ask
this :

is there any concept of "depends on" at all at the moment in org? I
don't see it if there is. e.g its quite possible to have a level one
task complete but a level 2 one incomplete.


** DONE PHP/HTTP authentication						   :WEB:
   SCHEDULED: <2007-10-13 Sat>
   - State "TODO"       [2007-10-12 Fri 01:30] \\
     get php /http authentication working
*** STARTED sub task
    SCHEDULED: <2007-10-12 Fri>
    - State "STARTED"    [2007-10-12 Fri 01:32] \\
      started
    - State "TODO"       [2007-10-12 Fri 01:31] \\
      blah

Re: clarification about org-mode

[Bastien]

Richard G Riley <rileyrgdev@googlemail.com> writes:

> is there any concept of "depends on" at all at the moment in org? 

Not strictly, but properties are inherited:

Doing (org-entry-get (point) "CATEGORY" t) on a headline will fetch the
category of the parent if this category is not defined for the headline.

,----[ org-entry-get ]
| Get value of property for entry at point-or-marker pom.
| If inherit is non-nil and the entry does not have the property,
| then also check higher levels of the hierarchy.
| If the property is present but empty, the return value is the empty string.
| If the property is not present at all, nil is returned.
`----

> don't see it if there is. e.g its quite possible to have a level one
> task complete but a level 2 one incomplete.

Yes it possible. 

-- 
Bastien