From: Kyle Meyer <kyle@kyleam.com>
To: Vikas Rawal <vikaslists@agrarianresearch.org>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: File local variables
Date: Fri, 12 Dec 2014 01:32:03 -0500 [thread overview]
Message-ID: <87vblh1iqk.fsf@kmlap.domain.org> (raw)
In-Reply-To: <87y4qd31ii.fsf@gmail.com> (Aaron Ecay's message of "Fri, 12 Dec 2014 00:01:09 -0500")
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
next prev parent reply other threads:[~2014-12-12 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 10:03 File local variables Vikas Rawal
2014-12-12 4:51 ` Vikas Rawal
2014-12-12 5:01 ` Aaron Ecay
2014-12-12 6:32 ` Kyle Meyer [this message]
2014-12-12 6:33 ` Vikas Rawal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vblh1iqk.fsf@kmlap.domain.org \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=vikaslists@agrarianresearch.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).