Rainer M Krug rai...@krugs.de writes:
This means *a specific property* - or *any property*? In other words:
can property A inherit from one level lower if property B is set in the
current level?
It can.
Then I think there is a bug. Look at the following example:
#+PROPERTY: header-args
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Rainer M Krug rai...@krugs.de writes:
This means *a specific property* - or *any property*? In other words:
can property A inherit from one level lower if property B is set in the
current level?
It can.
That's good.
Then I think there is a
Rainer M Krug rai...@krugs.de writes:
Ah. That explains.I think it would be quite useful to add this to the
info section of org-use-property-inheritance.
Patch welcome.
I agree - and I like the name accumulation properties or aggregation
properties.
Ditto. Any improvement to documentation
Rainer M Krug rai...@krugs.de writes:
Looking at my example, it seems that the variable
org-use-property-inheritance has no impact on the header arguments,
i.e. no properties are inherited. So it seems that there is a bug, or a
severe misunderstanding on my side what property inheritance
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Rainer M Krug rai...@krugs.de writes:
OK - but this behavior is not influenced by the variable
org-use-property-inheritance. So what is the meaning of the variable
then?
The variable is checked when calling `org-entry-get' with a non-nil
Rainer M Krug rai...@krugs.de writes:
OK - but this behavior is not influenced by the variable
org-use-property-inheritance. So what is the meaning of the variable
then?
The variable is checked when calling `org-entry-get' with a non-nil
INHERIT optional argument.
In this case
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
Charles C. Berry ccbe...@ucsd.edu writes:
On Fri, 29 May 2015, Rainer M Krug wrote:
Is this to be expected? I always thought, that the properties are
hierarchical, and that the ones from the lower levels / headers are used
as well?
Hello,
Charles C. Berry ccbe...@ucsd.edu writes:
On Fri, 29 May 2015, Rainer M Krug wrote:
Is this to be expected? I always thought, that the properties are
hierarchical, and that the ones from the lower levels / headers are used
as well?
I would have thought this, too.
Property
On Fri, 29 May 2015, Rainer M Krug wrote:
Consider this example:
I enable property inheritance with
(setq org-use-property-inheritance t)
But it does not matter. See the docstring for `org-entry-get'. The setting
used in `org-babel-view-src-block-info' for INHERIT is `t'.
I believe there
