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

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'

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

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

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

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

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

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

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

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

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

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: = # -*-

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

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.

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

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

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

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