Re: [O] org-export-babel-evaluate and header arguments

2016-03-10 Thread Charles C. Berry
On Thu, 10 Mar 2016, Anthony Cowley wrote: Charles C. Berry writes: On Wed, 9 Mar 2016, Anthony Cowley wrote: If I have org-export-babel-evaluate set to nil, source blocks are not evaluated on export. However, if a source block has a :var header argument that calls another source block, I

Re: [O] org-export-babel-evaluate and header arguments

2016-03-10 Thread Anthony Cowley
Charles C. Berry writes: > On Wed, 9 Mar 2016, Anthony Cowley wrote: > >> >> If I have org-export-babel-evaluate set to nil, source blocks are not >> evaluated on export. However, if a source block has a :var header >> argument that calls another source block, I am prompted if the callee >> sh

Re: [O] org-export-babel-evaluate and header arguments

2016-03-09 Thread Charles C. Berry
On Wed, 9 Mar 2016, Anthony Cowley wrote: If I have org-export-babel-evaluate set to nil, source blocks are not evaluated on export. However, if a source block has a :var header argument that calls another source block, I am prompted if the callee should be evaluated. Given that the caller

[O] org-export-babel-evaluate and header arguments

2016-03-09 Thread Anthony Cowley
If I have org-export-babel-evaluate set to nil, source blocks are not evaluated on export. However, if a source block has a :var header argument that calls another source block, I am prompted if the callee should be evaluated. Given that the caller is not to be evaluated, I'm not sure I see a r