From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: org-export-babel-evaluate and :exports none Date: Sat, 23 Feb 2013 09:08:53 +0100 Message-ID: <87mwuvih9m.fsf@gmail.com> References: <87hal9v0kq.fsf@gmail.com> <87a9r1z74c.fsf@Rainer.invalid> <877gm33sti.fsf@gmail.com> <87ppzsnkeu.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:41345) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U9AAW-0003cT-1z for emacs-orgmode@gnu.org; Sat, 23 Feb 2013 03:09:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U9AAN-0006ka-Kk for emacs-orgmode@gnu.org; Sat, 23 Feb 2013 03:09:15 -0500 Received: from mail-wg0-f54.google.com ([74.125.82.54]:41499) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U9AAN-0006jI-A1 for emacs-orgmode@gnu.org; Sat, 23 Feb 2013 03:09:07 -0500 Received: by mail-wg0-f54.google.com with SMTP id fm10so1084733wgb.33 for ; Sat, 23 Feb 2013 00:09:06 -0800 (PST) In-Reply-To: <87ppzsnkeu.fsf@Rainer.invalid> (Achim Gratz's message of "Fri, 22 Feb 2013 21:49:45 +0100") 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Achim Gratz Cc: emacs-orgmode@gnu.org Achim Gratz writes: > Nicolas Goaziou writes: >> I'm just starting over because that wasn't a correct solution. I'm not >> even sure about what bug this patch fixed. > > The bug was that Babel blocks were evaluated during export when > org-export-babel-evaluate was explicitly set to nil (the default value > is t). AFAICT, they aren't. Try the following in a buffer with `org-export-babel-evaluate' set alternatively to nil and t: #+BEGIN_SRC emacs-lisp :exports both :results value (+ 2 2) #+END_SRC >> Anyway, it isn't org-export-babel-evaluate's job to tell when to >> evaluate a source code block. > > The documentation says that its job is exactly that, if the context is > export. That was a typo. I meant "it isn't org-export-execute-babel-code's job ...". >> It may be org-babel-exp-process-buffer's. > > You call org-export-execute-babel-code however, which doesn't check the > above variable. It doesn't need to. Export = "ox.el", but export + babel = "ob-exp.el". So everything Babel related should happen there. So, /if there's a bug/, it should be fixed in ob-exp.el (maybe in `org-babel-exp-process-buffer's'), not in ox.el. Regards, -- Nicolas Goaziou