Hello,
When using this minimal configuration:
--8---cut here---start-8---
(setq org-agenda-prefix-format
'((agenda . %-11s%i %-12:c%?-12t%7e )
(timeline . % s)
(todo . %i %-12:c)
(search . %i %-12:c)
(tags . %i %-12:c)))
(setq org-agenda-files '(~/agenda.org))
--8---cut here---end---8---
where ~/agenda.org is:
--8---cut here---start-8---
* Projects
** Projet A
:PROPERTIES:
:Effort: 104:00
:END:
*** TODO Do this...
DEADLINE: 2014-03-20 Thu
*** TODO Do that as well!
DEADLINE: 2014-03-21 Fri
--8---cut here---end---8---
I did _not_ expect to see the effort of the whole project applied on every
of its subtasks:
--8---cut here---start-8---
Week-agenda (W12):
Monday 17 March 2014 W12
Tuesday18 March 2014
Wednesday 19 March 2014
Thursday 20 March 2014
Deadline: agenda: [104:00] TODO Do this...
Friday 21 March 2014
1 d. ago: agenda: [104:00] TODO Do this...
Deadline: agenda: [104:00] TODO Do that as well!
Saturday 22 March 2014
Sunday 23 March 2014
--8---cut here---end---8---
Just to confirm once more (than what's in the ECM), here is the value of
`org-use-property-inheritance':
╭
│ org-use-property-inheritance is a variable defined in `org.el'.
│ Its value is nil
│
│ Documentation:
│ Non-nil means properties apply also for sublevels.
│
│ This setting is chiefly used during property searches. Turning it on can
│ cause significant overhead when doing a search, which is why it is not
│ on by default.
│
│ When nil, only the properties directly given in the current entry count.
│ When t, every property is inherited. The value may also be a list of
│ properties that should have inheritance, or a regular expression matching
│ properties that should be inherited.
│
│ However, note that some special properties use inheritance under special
│ circumstances (not in searches). Examples are CATEGORY, ARCHIVE, COLUMNS,
│ and the properties ending in _ALL when they are used as descriptor
│ for valid values of a property.
╰
Am I missing something?
Best regards,
Seb
--
Sebastien Vauban
