From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Fenton Subject: Re: Babel - :export-dir and :file-ext arguments cause all blocks to emit files Date: Fri, 25 May 2018 21:52:02 +0200 Message-ID: <6427e745-9ca4-2356-a262-ef257082a9ce@pressure.to> References: <3ac2f42a-8ff2-1464-fa36-451e2ef0eacd@pressure.to> <87wovsprzd.fsf@nicolasgoaziou.fr> <87fu2f7sog.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43791) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fMIky-0002yO-Lo for emacs-orgmode@gnu.org; Fri, 25 May 2018 15:52:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fMIkv-0007Bj-Lb for emacs-orgmode@gnu.org; Fri, 25 May 2018 15:52:08 -0400 Received: from darwin.servwise.com ([31.193.138.136]:42116) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fMIkv-00079l-CA for emacs-orgmode@gnu.org; Fri, 25 May 2018 15:52:05 -0400 Received: from p578d3681.dip0.t-ipconnect.de ([87.141.54.129]:49052 helo=[192.168.178.25]) by darwin.servwise.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from ) id 1fMIkt-0003Re-5T for emacs-orgmode@gnu.org; Fri, 25 May 2018 19:52:03 +0000 In-Reply-To: <87fu2f7sog.fsf@gmail.com> Content-Language: en-GB 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: emacs-orgmode@gnu.org Hi Aaron > First of all, no issue arises with :output-dir alone. It can be > specified as a global header arg without issue. Yes, now I check again that's true. Thank you for clearing that up. > I designed :file-ext as a direct replacement for :file. That is, instead > of the above, one would specify: > > #+name: foo > #+begin_src R :file-ext pdf > ... > #+end_src > > and get the same result. IOW, the design was *not* for :file-ext to be > specified globally. Now I understand how it was intended (a shortcut for people who are scrupulous about using #+NAME) it makes sense. I was thinking it was meant as an easy way to switch globally between different formats (sometimes I want PDF for ease, sometimes I want Tikz for publication-quality, sometimes I want SVG for online etc.). > The change Nicolas proposes is how I would make :file-ext work if I were > writing it from scratch today, with the benefit of hindsight. I worry > that introducing it would break org documents in the wild, but maybe it is > worth it. You (all) are a better judge of what is a reasonable non-back-compatible change. all the best alex