Hello,
Jarmo Hurri writes:
> I have such documents regularly.
> 1. One type is a handout containing common contents at the beginning
>(included) and settings (setup).
> 2. The other case is a set of files sharing setup info and code (babel
>blocks, included).
Then I suggest to unravel
Greetings again.
Nicolas Goaziou writes:
>> 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.
>
> Again, there is no overlap between the two keywords. SETUPFILE is what
> you
Hello,
Jarmo Hurri writes:
> 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.
Again, there is no overlap between the two keywords. SETUPFILE is what
you want. INCLUDE is only
Hello Nicolas!
Nicolas Goaziou 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
Jarmo Hurri writes:
> Greetings.
>
> I am (still) trying to figure out a SINGLE common setup/include file for
> all settings for a large batch of files.
>
> I found out recently that common #properties can be set in a setup file
> (but not in an included file). However, now it seems that in a
