I've used the org-export-file (or somesuch) variable in the past which is only set during export.
Carsten Dominik <[email protected]> writes: > On 22.9.2013, at 14:22, Nicolas Goaziou <[email protected]> wrote: > >> Hello, >> >> Carsten Dominik <[email protected]> writes: >> >>> I am trying to write a function that will only run if it is called >>> during the evaluation of babel code during export, so basically during >>> `org-export-execute-babel code'. Do you know if there is a way to >>> detect that this is the case, >> >> There isn't. >> >>> or should I introduce a flag that is set by >>> `org-export-execute-babel-code'? >> >> This may be dangerous. Introducing such a flag means that Babel results >> may be different when exporting and when evaluating a block. > > This is exactly the point. I want to be able to create local variables > and change filter lists during export, while interactive evaluation should > not create local variables in the Org mode buffer. I do not plan to > advertise this flag, but to use it in one very specific function. > > Regards > > - Carsten >> >> >> Regards, >> >> -- >> Nicolas Goaziou > -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D
