Re: [O] HTML export with ":export" parameter with Orgmode 9.0

[Frederick Giasson]

Hi Charles,

Setting `org-export-babel-evaluate' to nil will ensure that NONE of 
your header arguments are followed.


Like the docstring says

 "Users who wish to avoid evaluating code on export should use the 
header argument ‘:eval never-export’."


It is tempting to `make-obsolete-variable' this variable and change 
its name to something that more completely describes what does not 
happen when set to nil.


Great, thanks for the clarification!

Take care,

Fred

Re: [O] HTML export with ":export" parameter with Orgmode 9.0

[Nicolas Goaziou]

Hello,

"Charles C. Berry"  writes:

> On Fri, 11 Nov 2016, Frederick Giasson wrote:
>
>> Hi Chuck,
>>
>>> even with a minimal init file.
>>>
>>> If you ever set the value of `org-export-babel-evaluate' to nil
>>> this might produce the behavior you describe. 
>>
>> Maybe, but as stated in the manual: "Setting the
>> org-export-babel-evaluate variable to nil will ensure that no code
>> blocks are evaluated as part of the export process."
>
> Argh! That paragraph needs to be revised.

Do you want to provide a patch for that?

> Like the docstring says
>
>  "Users who wish to avoid evaluating code on export should use the
> header argument ‘:eval never-export’."
>
> It is tempting to `make-obsolete-variable' this variable and change
> its name to something that more completely describes what does not
> happen when set to nil.

It can be done for Org 9.1.

Regards,

-- 
Nicolas Goaziou

Re: [O] HTML export with ":export" parameter with Orgmode 9.0

[Charles C. Berry]

On Fri, 11 Nov 2016, Frederick Giasson wrote:


Hi Chuck,


even with a minimal init file.

If you ever set the value of `org-export-babel-evaluate' to nil this might 
produce the behavior you describe. 


Maybe, but as stated in the manual: "Setting the org-export-babel-evaluate 
variable to nil will ensure that no code blocks are evaluated as part of the 
export process."


Argh! That paragraph needs to be revised.



From here: http://orgmode.org/manual/Exporting-code-blocks.html

The thing is that I indeed want to make sure that the code blocks are 
evaluated, but to me evaluation of code block is different than what to 
export from the Org file. It is often the case that I don't want export to 
evaluate anything, but just to export what is in the Org file's markup (while 
following what the header parameters say).




Setting `org-export-babel-evaluate' to nil will ensure that NONE of your 
header arguments are followed.


Like the docstring says

 "Users who wish to avoid evaluating code on export should use the header 
argument ‘:eval never-export’."


It is tempting to `make-obsolete-variable' this variable and change its 
name to something that more completely describes what does not happen when 
set to nil.


Chuck

Re: [O] HTML export with ":export" parameter with Orgmode 9.0

[Frederick Giasson]

Hi Chuck,


even with a minimal init file.

If you ever set the value of `org-export-babel-evaluate' to nil this 
might produce the behavior you describe. 


Maybe, but as stated in the manual: "Setting the 
org-export-babel-evaluate variable to nil will ensure that no code 
blocks are evaluated as part of the export process."


From here: http://orgmode.org/manual/Exporting-code-blocks.html

The thing is that I indeed want to make sure that the code blocks are 
evaluated, but to me evaluation of code block is different than what to 
export from the Org file. It is often the case that I don't want export 
to evaluate anything, but just to export what is in the Org file's 
markup (while following what the header parameters say).


Thanks,

Fred

Re: [O] HTML export with ":export" parameter with Orgmode 9.0

[Charles C. Berry]

On Fri, 11 Nov 2016, Frederick Giasson wrote:


Hi Nicolas,


It seems other users experienced it, yet it is unexpected and I cannot
reproduce it even with a minimal init file.


If you ever set the value of `org-export-babel-evaluate' to nil this might 
produce the behavior you describe.


In that case, see the docstring for advice.

HTH,

Chuck

Re: [O] HTML export with ":export" parameter with Orgmode 9.0

[Frederick Giasson]

Hi Nicolas,


It seems other users experienced it, yet it is unexpected and I cannot
reproduce it even with a minimal init file.


Ok I think I found the issue.

In all the files I worked on since I upgraded to 9.0 I had the following 
setting at the top of my org files:


=
# -*- org-export-babel-evaluate: nil -*-
=

In these notebooks, I don't want org-export to evaluate the code blocks, 
I want to do it manually (since some of them takes quite a while to run 
and I don't want to wait minutes to get an export).


In 8.x this was working perfectly. However, it appears that this 
behavior changed in 9.0. If I have that in place, then the :export 
header parameter is basically ignored and defaulted to "both".


Did this change and is this to be expected? If so, what should I use to 
get the same behavior?


Thanks!

Fred




Regards,

Re: [O] HTML export with ":export" parameter with Orgmode 9.0

[Frederick Giasson]

Hi Nicolas,


It seems other users experienced it, yet it is unexpected and I cannot
reproduce it even with a minimal init file.


Ok good. I will try to do some debugging on my side. I am wondering if 
it may not be a Windows issue, or some older 8.x configurations that may 
be at cause here.


Will keep you updated.

Thanks,

Fred

Re: [O] HTML export with ":export" parameter with Orgmode 9.0

[Nicolas Goaziou]

Hello,

Frederick Giasson  writes:

> Does this change impact the ":export [...]" code block header
> parameter? What I am often using is this:
>
>
> http://orgmode.org/manual/Exporting-code-blocks.html
>
>
> Which currently doesn't work but it is unclear from the release notes
> if it should or not and the code provided to fix the Export blocks
> doesn't appear to look for this syntax, so I guess it should still be
> working.
>
>
> Anybody else experience this issue?

It seems other users experienced it, yet it is unexpected and I cannot
reproduce it even with a minimal init file.

Regards,

-- 
Nicolas Goaziou

[O] HTML export with ":export" parameter with Orgmode 9.0

[Frederick Giasson]

Hi,


I am not clear about the change in the Export blocks that occurred in 
Org-mode 9.0



Does this change impact the ":export [...]" code block header parameter? 
What I am often using is this:



http://orgmode.org/manual/Exporting-code-blocks.html


Which currently doesn't work but it is unclear from the release notes if 
it should or not and the code provided to fix the Export blocks doesn't 
appear to look for this syntax, so I guess it should still be working.



Anybody else experience this issue?


Thanks,


Fred