From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Effort property inheritance?
Date: Fri, 21 Mar 2014 11:31:47 +0100 [thread overview]
Message-ID: <867g7nonak.fsf@somewhere.org> (raw)
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
Tuesday 18 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
next reply other threads:[~2014-03-21 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 10:31 Sebastien Vauban [this message]
2014-03-21 11:52 ` Effort property inheritance? Bastien
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=867g7nonak.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/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).