From mboxrd@z Thu Jan 1 00:00:00 1970 From: Derek Feichtinger Subject: Re: org-export-babel-evaluate=nil ignores ":exports results" setting - this has changed Date: Tue, 21 Feb 2017 07:05:54 +0100 Message-ID: <4a762d44-3d98-0caa-0e2d-3ff515f8f3c9@psi.ch> References: <38f5c7e0-b000-f8bd-97dd-6947e3272511@psi.ch> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48754) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cg3aN-0003aw-NV for emacs-orgmode@gnu.org; Tue, 21 Feb 2017 01:06:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cg3aI-0001O7-Mx for emacs-orgmode@gnu.org; Tue, 21 Feb 2017 01:06:03 -0500 Received: from edge20.ethz.ch ([82.130.99.26]:50667) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cg3aI-0001O1-CF for emacs-orgmode@gnu.org; Tue, 21 Feb 2017 01:05:58 -0500 In-Reply-To: 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: "Charles C. Berry" Cc: emacs-orgmode@gnu.org Hi Chuck On 21.02.2017 00:54, Charles C. Berry wrote: > On Mon, 20 Feb 2017, Derek Feichtinger wrote: > >> When org-export-babel-evaluate is set to nil, I see a different=20 >> behavior now as compared to earlier versions of org. > > Indeed. > > It is now *obsolete* and its behavior has intentionally been changed=20 > as noted here: > In my current version from MELPA the info text is not yet reflecting=20 this change. Thanks for pointing me to it. > ,----[ C-h v org-export-babel-evaluate RET ] > | org-export-babel-evaluate is a variable defined in =E2=80=98org-compat.= el=E2=80=99. > | Its value is t > | > | This variable is an alias for =E2=80=98org-export-use-babel=E2=80=99. > | This variable is obsolete since Org 9.1; > | use =E2=80=98org-export-use-babel=E2=80=99 instead. > > 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=20 > arbitrary code to be executed. The point of setting=20 > =E2=80=98org-export-use-babel=E2=80=99 or `org-export-babel-evaluate' to = nil was to=20 > prevent this. For that reason the former behavior was a bug. > OK. I can see that one wants to prevent most header args of babel blocks=20 from being reeavaluated, but the :exports argument does not affect=20 evaluation, but simply the representation of the result exported to the=20 target document. So, I think that this argument still should be=20 observed. Otherwise the resulting document would be completely changed=20 once I introduce =E2=80=98org-export-use-babel=E2=80=99. I might want to in= troduce it to=20 conserve the current code block results, while still being very much=20 interested in exporting it to a different format, or re-exporting it at=20 a later point (after having added new chapters that are manually evaluated)= . So, I still feel that this is a very much needed functionality that has=20 been lost on the way. I have made many documents over the last few years=20 that relied on this functionality, e.g. files collecting logs or=20 producing analysis results that were dependent on a particular state of=20 a system at that moment of time. I hope that the observing of the=20 :exports argument can be reintroduced. Derek --=20 Paul Scherrer Institut Dr. Derek Feichtinger Phone: +41 56 310 47 33 Section Head Science-IT Email: derek.feichtinger@psi.ch Building/Room No. WHGA/U126 CH-5232 Villigen PSI