I used to disable evaluation of source code when exporting by using the following as the first line: ;; -*- mode: Org; org-export-babel-evaluate: nil; -*- This is not working any more. Has something changed? My org-version is: Org-mode version 8.3beta (release_8.3beta-614-gc10ae1 @ /Users/vikas/.emacs.d/src/org-mode/lisp/) Vikas
> I used to disable evaluation of source code when exporting by using the following as the first line:
>
> ;; -*- mode: Org; org-export-babel-evaluate: nil; -*-
>
> This is not working any more. Has something changed?
>
> My org-version is: Org-mode version 8.3beta (release_8.3beta-614-gc10ae1 @ /Users/vikas/.emacs.d/src/org-mode/lisp/)
>
> Vikas
I think this is a bug. Could somebody confirm.
The following line shows up in the Latex export.
; -*- mode: org; org-export-babel-evaluate: nil -*-
Vikas
Hi Vikas, 2014ko abenudak 11an, Vikas Rawal-ek idatzi zuen: > >> I used to disable evaluation of source code when exporting by using the following as the first line: >> >> ;; -*- mode: Org; org-export-babel-evaluate: nil; -*- >> >> This is not working any more. Has something changed? >> >> My org-version is: Org-mode version 8.3beta (release_8.3beta-614-gc10ae1 @ /Users/vikas/.emacs.d/src/org-mode/lisp/) >> >> Vikas > > I think this is a bug. Could somebody confirm. I can’t confirm, in the sense that including that line in a file sets the buffer-local value of org-export-babel-evaluate to nil. If that variable isn’t having the effect of suppressing evaluation, that sounds like a bug, but it’s not clear that that is what is going on. Can you send an ECM? > > The following line shows up in the Latex export. > > ; -*- mode: org; org-export-babel-evaluate: nil -*- That is because ; is the comment syntax for (e)lisp. You probably want to begin the line with # instead. -- Aaron Ecay
Aaron Ecay <aaronecay@gmail.com> wrote: > 2014ko abenudak 11an, Vikas Rawal-ek idatzi zuen: >>> I used to disable evaluation of source code when exporting by using >>> the following as the first line: [...] >> I think this is a bug. Could somebody confirm. > > I can’t confirm, in the sense that including that line in a file sets > the buffer-local value of org-export-babel-evaluate to nil. > > If that variable isn’t having the effect of suppressing evaluation, > that sounds like a bug, but it’s not clear that that is what is going > on. Can you send an ECM? I can't confirm this either (using the following text). ,---- | # -*- org-export-babel-evaluate: nil; -*- | | #+begin_src emacs-lisp :exports both | (message "Evaluating?") | #+end_src | | #+RESULTS: | : Evaluating? `---- 'C-h v' indicates that the buffer-local value is indeed set to nil. The only place the value of org-export-babel-evaluate is checked is org-babel-exp-results. Exporting the example above with org-babel-exp-results edebugged shows that the main body of that function doesn't execute. So, the code isn't being evaluated at export, unless it's happening elsewhere. How are you checking that the code is evaluated at export? -- Kyle
>>
>> I can’t confirm, in the sense that including that line in a file sets
>> the buffer-local value of org-export-babel-evaluate to nil.
>>
>> If that variable isn’t having the effect of suppressing evaluation,
>> that sounds like a bug, but it’s not clear that that is what is going
>> on. Can you send an ECM?
>
> I can't confirm this either (using the following text).
>
> ,----
> | # -*- org-export-babel-evaluate: nil; -*-
> |
> | #+begin_src emacs-lisp :exports both
> | (message "Evaluating?")
> | #+end_src
> |
> | #+RESULTS:
> | : Evaluating?
> `----
Thanks Aaron and Kyle.
I perhaps confused the fact that the line which started with a ; was showing up in the export to understand that the line was not being treated as it should.
But in my earlier org files, I always started this line with a ; and it used to work fine. Perhaps (perhaps), the behaviour has changed in terms of not treating lines starting with ; as comments in org.
Be that as it may, starting the line with a # works.
Thanks again,
Vikas