Nicolas Goaziou 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
Hello,
Jarmo Hurri 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?
Regards,
--
Nicolas Goaziou
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
