Hello Nicolas!
Nicolas Goaziou <m...@nicolasgoaziou.fr> writes: > SETUPFILE and INCLUDE are orthogonal. There is no point in mixing > them. Ok. As a programmer I was hoping to mix them, because it would be logical to have _one_ header file that defines all the common things for a set of related files. But perhaps I can get away with using SETUPFILEs only. I will see. > Jarmo Hurri <jarmo.hu...@iki.fi> writes: >> Documentation of #setupfile says that >> >> "Org parses the contents of this document as if it was included in the >> buffer." >> >> https://orgmode.org/manual/In_002dbuffer-settings.html >> >> But that does not seem to be the case. > > SETUPFILE keyword recursively loads configuration from other files, > without inserting anything. INCLUDE keyword recursively inserts > contents from other files in the current document, but there is no > guarantee that configuration from these files will be inherited. Do I understand correctly: the description in the documentation is not correct in the sense that not all contents from SETUPFILE is evaluated as if it were included in the buffer? I am just trying to think about how this limitation, if it exists, should be expressed in documentation. Shall I give it a try? Thanks for the clarifying response! Jarmo
