:exports not being respected

:exports not being respected

[Vikas Rawal]

I have a with just the following header, and it is not respecting :exports in my R source blocks. The pdf file created has source code as well as the results.

What is wrong? Has the syntax changed again? I have not done anything with org-export-babel-evaluate.

#+TITLE: Title of this document
#+TODO: NOTES EXERCISE | DONE
#+OPTIONS: toc:nil
#+LATEX_CLASS: article
#+PROPERTY: header-args :eval never-export
#+PROPERTY: header-args :session ec404


I am on Org-mode version 8.3.5 (release_8.3.5-1026-g096f42)

Vikas

Re: :exports not being respected

[Charles C. Berry]

On Wed, 10 Aug 2016, Vikas Rawal wrote:

> I have a with just the following header, and it is not respecting 
> :exports in my R source blocks. The pdf file created has source code as 
> well as the results.
>
> What is wrong?

No ECM with src blocks, but see below.

> Has the syntax changed again? I have not done anything with org-export-babel-evaluate.
>
> #+TITLE: Title of this document
> #+TODO: NOTES EXERCISE | DONE
> #+OPTIONS: toc:nil
> #+LATEX_CLASS: article
> #+PROPERTY: header-args :eval never-export
> #+PROPERTY: header-args :session ec404

Missing *plus* sign! (Don't forget `C-c C-c' !)

#+PROPERTY: header-args+ :session ec404

>
>
> I am on Org-mode version 8.3.5 (release_8.3.5-1026-g096f42)

Works as expected for :exports both/results/code/none on:

Org-mode version 8.3.5 (release_8.3.5-1061-g48a87)
Org-mode version 8.3.5 (release_8.3.5-1025-g67c29a)


Chuck

p.s. It often helps to be sure header-args are what you thought they 
should be, i.e. move to a src block and run C-c C-v C-i. Doing that I 
could see that your second header-args property line overruled the first 
one.