From: Jarmo Hurri <jarmo.hurri@iki.fi>
To: emacs-orgmode@gnu.org
Subject: Included global properties not inherited: bug or feature?
Date: Fri, 06 Dec 2019 12:55:00 +0200 [thread overview]
Message-ID: <87h82dd8qj.fsf@iki.fi> (raw)
Greetings.
It seems that when a file with global properties is included, the global
properties are not inherited. Is this a bug or a feature?
Consider the two files inlined below:
# ---------------------------------- file 'included.org' -------------------
#+property: MY_INCLUDED_PROPERTY some included value
# --------------------------------------------------------------------------
# -------------- file which includes ---------------------------------------
#+include: included.org :only-contents nil
#+property: MY_INLINE_PROPERTY some inline value
src_elisp[:exports results :results raw]{(org-entry-get nil "MY_INCLUDED_PROPERTY" t)} nil
src_elisp[:exports results :results raw]{(org-entry-get nil "MY_INLINE_PROPERTY" t)} some inline value
# --------------------------------------------------------------------------
As you can see from the results of evaluation of elisp blocks, the
included global property is not available in the including file. Note
that the documentation for #include states that there is a special
property :only-contents for including only contents, not properties. To
play it safe, I have set this property to 'nil' above.
https://orgmode.org/manual/Include-files.html
Based on this documentation, I was expecting global properties to be
available by default in including files.
I find current behaviour inconvenient, because I want to set common
global properties for a large number of files, and I can not currently
do this via an included file.
What is the verdict?
I am running
Org mode version 9.3 (release_9.3-34-g2eee3c)
GNU Emacs 26.2
Jarmo
next reply other threads:[~2019-12-06 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 10:55 Jarmo Hurri [this message]
2019-12-06 20:41 ` Included global properties not inherited: bug or feature? Nicolas Goaziou
2019-12-07 6:28 ` Jarmo Hurri
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=87h82dd8qj.fsf@iki.fi \
--to=jarmo.hurri@iki.fi \
--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).