From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ista Zahn Subject: Re: exporting documents w/ babel results w/o evaluating babel blocks Date: Tue, 24 May 2016 10:32:13 -0400 Message-ID: References: <878addc2b6b14ce99e907921f0985d24@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> <87a8jkoec6.fsf@ucl.ac.uk> <87wpmomz6x.fsf@ucl.ac.uk> <871t4wd0to.fsf@alphaville.usersys.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55682) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b5DNt-0004eo-52 for emacs-orgmode@gnu.org; Tue, 24 May 2016 10:32:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b5DNq-0008J0-Nn for emacs-orgmode@gnu.org; Tue, 24 May 2016 10:32:36 -0400 Received: from mail-oi0-x22a.google.com ([2607:f8b0:4003:c06::22a]:32918) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b5DNq-0008Is-Ik for emacs-orgmode@gnu.org; Tue, 24 May 2016 10:32:34 -0400 Received: by mail-oi0-x22a.google.com with SMTP id k23so29169521oih.0 for ; Tue, 24 May 2016 07:32:34 -0700 (PDT) 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: Andreas Kiermeier Cc: Nick Dokos , emacs-orgmode , "Charles C. Berry" , Grant Rettke On Tue, May 24, 2016 at 6:17 AM, Andreas Kiermeier wrote: > I second that. > I like exporting everything to LaTeX without having to re-run all the code, > which in many cases can add considerable time. Which you can still do, I guess by (setq org-babel-default-header-args (cons '(:eval . "never-export") (assq-delete-all :noweb org-babel-default-header-args))) instead of the old way (setq org-export-babel-evaluate nil) I'm not saying this is good or right. IMO the old behavior of org-export-babel-evaluate made sense and was useful; the new behavior is surprising and I have a hard time seeing how it is useful. One can argue (as Chuck has) that the new behavior is fine sense we have another way of achieving the desired results; that may be, but I have yet to see an explanation of why the new behavior is desirable. It this change is not going to be reversed than the doc string for org-export-babel-evaluate needs to be updated, and something should go in the NEWS file warning people (like me) who have been relying on the old behavior. Best, Ista > Cheers, > Andreas > > On 24 May 2016 at 11:04, Grant Rettke wrote: >> >> On Sun, May 22, 2016 at 4:52 PM, Charles C. Berry >> wrote: >> > TL;DR: Org babel headers give excellent control over what gets run, >> > when it gets run, and how. Users should use them. >> >> Definitely! >> >> > Don't reset `org-export-babel-evaluate'. >> >> Why not? >> >> It can be nice to disable org-export-babel-evaluate by setting it to >> `nil'. >> >> That way you separate your workflow into two distinct steps: one for >> execution and one for weaving. >> >> It would be fun to "see" everyone's Org-Mode workflows; I bet there >> are a lot of nice approaches. >> >