Nicolas Goaziou <m...@nicolasgoaziou.fr> writes:
>> 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 happens if you use SETUPFILE instead?
It works perfectly.
Please find attached a patch that mentions this behaviour in the
include-part of Org manual. Ok?
Jarmo
>From 00701e1732fcf71180dc02f72117b44bccf5eb2d Mon Sep 17 00:00:00 2001
From: Jarmo Hurri <jarmo.hu...@iki.fi>
Date: Sat, 7 Dec 2019 08:19:05 +0200
Subject: [PATCH] org-manual.org: Document global properties not being
inherited when including files
* doc/org-manual.org: Note that when an org-file is included, even
with `:only-contents` set to `nil`, global properties set with lines
beginning `#+PROPERTY:` will not be inherited in the file that
includes. Point the user to use `#+SETUPFILE:` for this purpose.
---
doc/org-manual.org | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 35f6013ce..a0aedf825 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -11770,6 +11770,11 @@ with the custom ID =theory=, you can use
: #+INCLUDE: "./paper.org::#theory" :only-contents t
+Note that even when =:only-contents= has value ~nil~, properties set
+in the included file by lines beginning with =#+PROPERTY:= will not be
+inherited in the file that includes. To achieve such inheritance, use
+=#+SETUPFILE:= instead (see [[Summary of In-Buffer Settings]]).
+
The following command allows navigating to the included document:
- {{{kbd(C-c ')}}} (~org-edit~special~) ::
--
2.21.0
