From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Charles C. Berry" Subject: Re: org-export-babel-evaluate=nil ignores ":exports results" setting - this has changed Date: Mon, 20 Feb 2017 15:54:59 -0800 Message-ID: References: <38f5c7e0-b000-f8bd-97dd-6947e3272511@psi.ch> Mime-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY="0-2060827784-1487634899=:2883" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45671) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cfxnP-0001QE-88 for emacs-orgmode@gnu.org; Mon, 20 Feb 2017 18:55:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cfxnM-00052A-61 for emacs-orgmode@gnu.org; Mon, 20 Feb 2017 18:55:07 -0500 Received: from iport-acv6-out.ucsd.edu ([132.239.0.13]:7643) by eggs.gnu.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.71) (envelope-from ) id 1cfxnL-00051U-Kc for emacs-orgmode@gnu.org; Mon, 20 Feb 2017 18:55:04 -0500 In-Reply-To: <38f5c7e0-b000-f8bd-97dd-6947e3272511@psi.ch> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Derek Feichtinger Cc: emacs-orgmode@gnu.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-2060827784-1487634899=:2883 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT 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 --0-2060827784-1487634899=:2883--