From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Rainer M Krug <Rainer@krugs.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-use-property-inheritance not working?
Date: Fri, 29 May 2015 12:01:15 -0700 [thread overview]
Message-ID: <alpine.OSX.2.11.1505291136130.449@charles-berrys-macbook.local> (raw)
In-Reply-To: <m2iobbvbnh.fsf@krugs.de>
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 is a problem with `org-entry-get'. Here is an ECM:
--8<---------------cut here---------------start------------->8---
#+PROPERTY: aprop one
#+BEGIN_SRC emacs-lisp
(org-entry-get (point) "aprop" t)
#+END_SRC
#+RESULTS:
: one
* x
:PROPERTIES:
:aprop+: two
:END:
#+BEGIN_SRC emacs-lisp
(org-entry-get (point) "aprop" t)
#+END_SRC
#+RESULTS:
: one two
** y
:PROPERTIES:
:aprop+: three
:END:
#+BEGIN_SRC emacs-lisp
(org-entry-get (point) "aprop" t)
#+END_SRC
#+RESULTS:
: one three
I expected 'one two three'
--8<---------------cut here---------------end--------------->8---
[much deleted]
>
> 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.
[rest deleted]
Chuck
next prev parent reply other threads:[~2015-05-29 19:01 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 [this message]
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
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=alpine.OSX.2.11.1505291136130.449@charles-berrys-macbook.local \
--to=ccberry@ucsd.edu \
--cc=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).