From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Babel CALL no longer produces HTML output Date: Mon, 25 Jul 2016 09:08:01 +0200 Message-ID: <87wpkaw5ym.fsf@saiph.selenimh> References: <87r3akzh3c.fsf@iki.fi> <87fur0fgbh.fsf@saiph.selenimh> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51331) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bRZzh-0000lb-9p for emacs-orgmode@gnu.org; Mon, 25 Jul 2016 03:08:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bRZzf-0004A3-4r for emacs-orgmode@gnu.org; Mon, 25 Jul 2016 03:08:04 -0400 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:35140) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bRZze-00049f-V5 for emacs-orgmode@gnu.org; Mon, 25 Jul 2016 03:08:03 -0400 In-Reply-To: (Charles C. Berry's message of "Sat, 23 Jul 2016 15:16:01 -0700") 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: Jarmo Hurri , emacs-orgmode@gnu.org Hello, "Charles C. Berry" writes: > On Sat, 23 Jul 2016, Nicolas Goaziou wrote: >> OTOH, inheriting :exports property may not be optimal. In particular, >> ":exports code" for a Babel call is probably nonsensical. Perhaps >> a solution would be to keep the current behaviour and make an exception >> for :exports, which would always be `results' for Babel calls. >> >> WDYT? > > I think that would work well enough. Funnily, that's what the previous evaluation process did. I was confused by the "default" part in `org-babel-default-lob-header-args'. I realize that this variable is no replacement for `org-babel-default-header-args'. It permits to override headers inherited from the source block instead. This is now fixed. I updated variable docstring accordingly. > Although I might quibble about what 'local' means here. If the src > block is under a headline called XYZ with a `header-args' property of > `:eval no' and the babel call is under headline ABC with no > header-args property, I think some would expect the default to take > precedence for calls under ABC over the property in XYZ. The point is that a Babel call without any header argument or node property defined at point of call should behave exactly as the src block being called (minus the :exports behaviour, per above). It seems logical to me that a source block that cannot be evaled cannot be, by default, called either. You may want to add (:eval . "yes") to `org-babel-default-lob-header-args' if you disagree. Regards, -- Nicolas Goaziou