On Mon, Feb 05 2024, Ihor Radchenko <yanta...@posteo.net> wrote: > Leo Butler <leo.but...@umanitoba.ca> writes: > >> Q: if #+setupfile points to a real file available to download, does Org >> evaluate that file? > > keywords and startup options are taken from there. No Elisp code present > in #+SETUPFILE is evaluated. > > That said, if the file defines babel header arguments with elisp or > "eval" macros, they may be used later, during export or when src block > evaluation is requested by the user.
So, it is *possible* to have the setupfile set-up arbitrary elisp code that would be evaluated at some later time (during export or src block evaluation, as you wrote)? Is that correct? Leo
