From: Rainer M Krug <Rainer@krugs.de>
To: emacs-orgmode@gnu.org
Subject: Re: org-use-property-inheritance not working?
Date: Mon, 01 Jun 2015 18:15:20 +0200 [thread overview]
Message-ID: <m2vbf7jtgn.fsf@krugs.de> (raw)
In-Reply-To: <87k2vnto37.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Mon, 01 Jun 2015 18:01:16 +0200")
[-- Attachment #1: Type: text/plain, Size: 4696 bytes --]
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Rainer M Krug <Rainer@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 bug. Look at the following example:
>>
>> #+PROPERTY: header-args :tangle-mode (identity #o444)
>> #+PROPERTY: header-args+ :eval no-export
>>
>> #+PROPERTY: header-args:R :session *R.EnergyBalance*
>>
>>
>> * Make sure org-use-property-inheritance is nil
>>
>> #+begin_src emacs-lisp
>> (setq org-use-property-inheritance nil)
>> #+end_src
>>
>> #+RESULTS:
>>
>> Therefore from now on, we will only look at the current level and
>> ignore properties set at lower levels - correct?
>>
>> * Without properties
>> #+begin_src
>> 13
>> #+end_src
>>
>> ,----
>> | Properties:
>> | :header-args :tangle-mode (identity #o444) :eval no-export
>> | :header-args:nil nil
>> | Switches:
>> | Header Arguments:
>> | :cache no
>> | :eval no-export
>> | :exports code
>> | :hlines no
>> | :noweb no
>> | :results replace
>> | :session none
>> | :tangle no
>> | :tangle-mode 292
>> `----
>>
>> * With Properties at level one
>> :PROPERTIES:
>> :header-args+: :tangle SetAtFirstLevel
>> :header-args+: :output-dir ./output
>> :END:
>>
>> #+begin_src R
>> 13
>> #+end_src
>>
>> ,----
>> | Lang: R
>> | Properties:
>> | :header-args :tangle-mode (identity #o444) :eval no-export :tangle SetAtFirstLevel :output-dir ./output
>> | :header-args:R :session *R.EnergyBalance*
>> | Header Arguments:
>> | :cache no
>> | :eval no-export
>> | :exports code
>> | :hlines no
>> | :noweb no
>> | :output-dir ./output
>> | :results replace
>> | :session *R.EnergyBalance*
>> | :tangle ./output/scripts/analysisCode.do.not.source.R
>> | :tangle-mode 292
>> `----
>>
>> ** Second level without properties
>> These should now be the same as [[Without properties]] as org-use-property-inheritance is nil.
>> #+begin_src R
>> cat(13)
>> #+end_src
>>
>> But it is the same as [[With Properties at level one]].
>> ,----
>> | Lang: R
>> | Properties:
>> | :header-args :tangle-mode (identity #o444) :eval no-export :tangle SetAtFirstLevel :output-dir ./output
>> | :header-args:R :session *R.EnergyBalance*
>> | Header Arguments:
>> | :cache no
>> | :eval no-export
>> | :exports code
>> | :hlines no
>> | :noweb no
>> | :output-dir ./output
>> | :results replace
>> | :session *R.EnergyBalance*
>> | :tangle ./output/scripts/analysisCode.do.not.source.R
>> | :tangle-mode 292
>> `----
>
> There's no bug.
>
> Babel activates inheritance on purpose, no matter what
> `org-use-property-inheritance' says. See the last line of its docstring:
> "ob-core.el" (in particular `org-babel-view-src-block-info') calls
> `org-entry-get' with `t', not `selective'.
>
> Really, `org-use-property-inheritance' is for your own properties. Org
> ignores it to handle its own internal properties.
Ah. That explains.I think it would be quite useful to add this to the
info section of org-use-property-inheritance.
>
>> Concerning property accumulation: I assume you mean the header-args+ -
>> correct? Because I could not find the term "accumu" in the org manual.
>
> Correct.
>
> I don't think they have a name, but they should, because they are
> a different beast than regular properties.
>
I agree - and I like the name "accumulation properties" or "aggregation
properties".
>> Are these properties treated as a normal properties, and the same rules
>> apply, or are there specific rules?
>
> They follow specific rules. For example there can only be one property
> A in a given property drawer, but there can be as many A+ as you want.
> Also, (org-entry-get (point) "A+") will not return something meaningful.
Thanks - things are much clearer now.
So there is no way at the moment to define a property in lower level
and then overwrite it in a higher level? It might be only me, but I
think that would be quite a useful addition.
Thanks a lot for your help,
Rainer
>
>
> Regards,
--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax : +33 - (0)9 58 10 27 44
Fax (D): +49 - (0)3 21 21 25 22 44
email: Rainer@krugs.de
Skype: RMkrug
PGP: 0x0F52F982
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]
next prev parent reply other threads:[~2015-06-01 16:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 11:57 org-use-property-inheritance not working? Rainer M Krug
2015-05-29 19:01 ` Charles C. Berry
2015-05-29 22:21 ` Nicolas Goaziou
2015-05-30 11:04 ` Rainer M Krug
2015-05-30 22:49 ` Nicolas Goaziou
2015-05-31 11:46 ` Rainer M Krug
2015-05-31 22:17 ` Nicolas Goaziou
[not found] ` <m24mmrlssh.fsf@krugs.de>
2015-06-01 16:01 ` Nicolas Goaziou
2015-06-01 16:15 ` Rainer M Krug [this message]
2015-06-01 17:11 ` Nicolas Goaziou
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=m2vbf7jtgn.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=emacs-orgmode@gnu.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).