Re: [O] org-export-babel-evaluate=nil ignores ":exports results" setting - this has changed

2017-02-22 Thread Colin Baxter
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

Re: [O] org-export-babel-evaluate=nil ignores ":exports results" setting - this has changed

2017-02-22 Thread Colin Baxter
Hi. On Tue, Feb 21 2017, Charles C. Berry wrote: > On Mon, 20 Feb 2017, Derek Feichtinger wrote: > >> Hi Chuck >> >> On 21.02.2017 00:54, Charles C. Berry wrote: >>> On Mon, 20 Feb 2017, Derek Feichtinger wrote: >>> When org-export-babel-evaluate is set to nil, I see a different

Re: [O] org-export-babel-evaluate=nil ignores ":exports results" setting - this has changed

2017-02-22 Thread Derek Feichtinger
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: Hi Chuck On 21.02.2017 00:54, Charles C. Berry wrote: On Mon, 20 Feb 2017, Derek Feichtinger wrote: When org-export-babel-evaluate is set to

Re: [O] org-export-babel-evaluate=nil ignores ":exports results" setting - this has changed

2017-02-21 Thread Charles C. Berry
On Tue, 21 Feb 2017, Aaron Ecay wrote: Hi Chuck, 2017ko otsailak 20an, "Charles C. Berry"-ek idatzi zuen: [...] Allowing header args to be processed (as before) also allows for arbitrary code to be executed. The point of setting ‘org-export-use-babel’ or `org-export-babel-evaluate' to

Re: [O] org-export-babel-evaluate=nil ignores ":exports results" setting - this has changed

2017-02-21 Thread Charles C. Berry
On Mon, 20 Feb 2017, Derek Feichtinger wrote: Hi Chuck On 21.02.2017 00:54, Charles C. Berry wrote: On Mon, 20 Feb 2017, Derek Feichtinger wrote: When org-export-babel-evaluate is set to nil, I see a different behavior now as compared to earlier versions of org. Indeed. It is now

Re: [O] org-export-babel-evaluate=nil ignores ":exports results" setting - this has changed

2017-02-21 Thread Aaron Ecay
Hi Chuck, 2017ko otsailak 20an, "Charles C. Berry"-ek idatzi zuen: [...] > > Allowing header args to be processed (as before) also allows for arbitrary > code to be executed. The point of setting ‘org-export-use-babel’ or > `org-export-babel-evaluate' to nil was to prevent this. For that

Re: [O] org-export-babel-evaluate=nil ignores ":exports results" setting - this has changed

2017-02-20 Thread Derek Feichtinger
Hi Chuck On 21.02.2017 00:54, Charles C. Berry wrote: On Mon, 20 Feb 2017, Derek Feichtinger wrote: When org-export-babel-evaluate is set to nil, I see a different behavior now as compared to earlier versions of org. Indeed. It is now *obsolete* and its behavior has intentionally been

Re: [O] org-export-babel-evaluate=nil ignores ":exports results" setting - this has changed

2017-02-20 Thread Charles C. Berry
On Mon, 20 Feb 2017, Derek Feichtinger wrote: When org-export-babel-evaluate is set to nil, I see a different behavior now as compared to earlier versions of org. Indeed. It is now *obsolete* and its behavior has intentionally been changed as noted here: ,[ C-h v

[O] org-export-babel-evaluate=nil ignores ":exports results" setting - this has changed

2017-02-20 Thread Derek Feichtinger
When org-export-babel-evaluate is set to nil, I see a different behavior now as compared to earlier versions of org. Now it seems that all header arguments of a code block are ignored, including the arguments to the :exports setting. Even when I have set ":exports results" or ":exports code"