On Wed, Feb 22 2017, Derek Feichtinger wrote: Dear Derek,
> Hi Colin > > On 22.02.2017 16:27, Colin Baxter wrote: >> Hi. >> >> On Tue, Feb 21 2017, Charles C. Berry wrote: >> >>> On Mon, 20 Feb 2017, Derek Feichtinger wrote: >>> --------- snip --------- > Based on the documentation one can set the header arguments system wide > using these variables: > > org-babel-default-header-args (for all) > org-babel-default-header-args:<lang> (language specific) > > File wide using PROPERTY: > > #+PROPERTY: header-args :eval never-export > > Org heading wide using a local property setting: > * sample header > :PROPERTIES: > :header-args: :eval never-export > :END: > > The last two ways I tested. So, in the end, with some changes to most of > my files I can get the same behavior again, which is good. > > It's a matter of taste or use case whether to define the default > behavior to eval on export. I would have made the case the eval on > export is the more rare use case. I almost never have this, except for > certain kinds of reports, e.g. if you want to gather the state of a > server with a number of prepared queries in the org file. For me, most > org files are like a number of measurements taken at a certain point in > time, and I want to conserve the output of the evaluation exactly like > it was. E.g. when working at speeding up code, I very much like to do > the whole thing inside of an org file where I document the speed > measurements, my changes to code and what the effect was. So, more like > some kind of interactive lab journal. > > But as I said, it is a matter of taste, and I am happy that I can get > the original functionality without too much effort. > > Best regards, > Derek --------------- snip --------- Thank you, I really appreciate this information. You have saved me a couple of hours work. I'll probably end up setting org-babel-default-header-args as a local variable. Thanks again. Best wishes.
