On 2015-04-29 17:05, Nicolas Goaziou writes:
> Hello,
>
> Alan Schmitt writes:
>
>> Does this mean that #+INCLUDE is now a superset of #+SETUPFILE (I've had
>> some cases where I needed to do both)?
>
> No, it isn't.
>
> INCLUDE are expanded only during export. SETUPFILE are read whenever you
>
Hello,
Alan Schmitt writes:
> Does this mean that #+INCLUDE is now a superset of #+SETUPFILE (I've had
> some cases where I needed to do both)?
No, it isn't.
INCLUDE are expanded only during export. SETUPFILE are read whenever you
open a document or use C-c C-c on a keyword.
Regards,
--
Ni
On 2015-04-27 20:46, Nicolas Goaziou writes:
>>> Set-up (e.g., link abbreviations) is not refreshed after expanding
>>> INCLUDE keywords. I cannot remember why, tho. Maybe for (dubious)
>>> efficiency reasons.
>>
>> If you don't remember, may be it would be possible to try it out?
>> Would love i
>
> >> Set-up (e.g., link abbreviations) is not refreshed after expanding
> >> INCLUDE keywords. I cannot remember why, tho. Maybe for (dubious)
> >> efficiency reasons.
> >
> > If you don't remember, may be it would be possible to try it out?
> > Would love it and as a feature it looks natural fo
Detlef Steuer writes:
> The real file2.org is somewhat big and would be scanned completely,
> wouldn't it?
Only special keywords are parsed.
The advantage of SETUPFILE is that it works even outside of export.
>> Set-up (e.g., link abbreviations) is not refreshed after expanding
>> INCLUDE keyw
> Hello,
>
> Detlef Steuer writes:
>
> > I have two files:
> >
> > file1.org:
> >
> > #+LINK: HOME http://example.de
> >
> > * My Homepage You can find my homepage [[HOME][here]]
> >
> > #+INCLUDE: file2.org
> >
> >
> > file2.org
> >
Hello,
Detlef Steuer writes:
> I have two files:
>
> file1.org:
>
> #+LINK: HOME http://example.de
>
> * My Homepage You can find my homepage [[HOME][here]]
>
> #+INCLUDE: file2.org
>
>
> file2.org
> #+LINK: HOME2 http://other.exampl
