From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Derek Feichtinger <derek.feichtinger@psi.ch>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-export-babel-evaluate=nil ignores ":exports results" setting - this has changed
Date: Mon, 20 Feb 2017 15:54:59 -0800 [thread overview]
Message-ID: <alpine.OSX.2.20.1702201539500.2883@charles-berrys-macbook.local> (raw)
In-Reply-To: <38f5c7e0-b000-f8bd-97dd-6947e3272511@psi.ch>
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
On Mon, 20 Feb 2017, Derek Feichtinger wrote:
> When org-export-babel-evaluate is set to nil, I see a different behavior now
> as compared to earlier versions of org.
Indeed.
It is now *obsolete* and its behavior has intentionally been changed as
noted here:
,----[ C-h v org-export-babel-evaluate RET ]
| org-export-babel-evaluate is a variable defined in ‘org-compat.el’.
| Its value is t
|
| This variable is an alias for ‘org-export-use-babel’.
| This variable is obsolete since Org 9.1;
| use ‘org-export-use-babel’ instead.
|
| Documentation:
| Switch controlling code evaluation and header processing during export.
| When set to nil no code will be evaluated as part of the export
| process and no header arguments will be obeyed. When set to
| ‘inline-only’, only inline code blocks will be executed. Users
| who wish to avoid evaluating code on export should use the header
| argument ‘:eval never-export’.
|
| You can customize this variable.
|
| [back]
`----
and here
(info "(org) Exporting code blocks")
> I think that this should be considered a bug.
Allowing header args to be processed (as before) also allows for arbitrary
code to be executed. The point of setting ‘org-export-use-babel’ or
`org-export-babel-evaluate' to nil was to prevent this. For that reason
the former behavior was a bug.
Chuck
next prev parent reply other threads:[~2017-02-20 23:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 22:02 org-export-babel-evaluate=nil ignores ":exports results" setting - this has changed Derek Feichtinger
2017-02-20 23:54 ` Charles C. Berry [this message]
2017-02-21 6:05 ` Derek Feichtinger
2017-02-21 16:37 ` Charles C. Berry
2017-02-22 15:27 ` Colin Baxter
2017-02-22 15:45 ` Derek Feichtinger
2017-02-22 18:56 ` Colin Baxter
2017-02-21 10:51 ` Aaron Ecay
2017-02-21 16:40 ` Charles C. Berry
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=alpine.OSX.2.20.1702201539500.2883@charles-berrys-macbook.local \
--to=ccberry@ucsd.edu \
--cc=derek.feichtinger@psi.ch \
--cc=emacs-orgmode@gnu.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).