From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Fenton Subject: Babel - :export-dir and :file-ext arguments cause all blocks to emit files Date: Thu, 24 May 2018 23:50:30 +0200 Message-ID: <3ac2f42a-8ff2-1464-fa36-451e2ef0eacd@pressure.to> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------2DA3F1CEAD35B6AFDD462158" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60387) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fLyed-00020p-8N for emacs-orgmode@gnu.org; Thu, 24 May 2018 18:24:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fLyeZ-0008T8-4N for emacs-orgmode@gnu.org; Thu, 24 May 2018 18:24:15 -0400 Received: from darwin.servwise.com ([31.193.138.136]:60598) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fLyeY-0008Jd-Qd for emacs-orgmode@gnu.org; Thu, 24 May 2018 18:24:11 -0400 Received: from p578d3681.dip0.t-ipconnect.de ([87.141.54.129]:46558 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 1fLy7z-0002fE-2v for emacs-orgmode@gnu.org; Thu, 24 May 2018 21:50:31 +0000 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 This is a multi-part message in MIME format. --------------2DA3F1CEAD35B6AFDD462158 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi, As far I understand it, |:output-dir| and |:file-ext| that were intended to be used in the global document header, applying to all blocks. However, it seems to mean that all blocks regardless of their :results args then emit a file, and put their output as a [file:] link. It's not clear from the docs why this happens. Am I missing something, or does this mean that these arguments are useless unless a document happens only to emit graphics from blocks? At the moment, the blocks (R, as it happens) are meant to sometimes emit scalars, sometimes literal latex, sometimes tables to be formatted by orgs, and sometimes graphics. But all the non-graphics are at the moment being stuffed into (non-working) PDF files. Following a discussion and suggested, but not-working solution at: https://emacs.stackexchange.com/questions/41618/org-modes-output-dir-and-file-ext-arguments-cause-all-output-to-be-saved-to Thanks alex --------------2DA3F1CEAD35B6AFDD462158 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

Hi,

As far I understand it, :output-dir and :file-ext that were intended to be used in the global document header, applying to all blocks.

However, it seems to mean that all blocks regardless of their :results args then emit a file, and put their output as a [file:] link. It's not clear from the docs why this happens.

Am I missing something, or does this mean that these arguments are useless unless a document happens only to emit graphics from blocks? At the moment, the blocks (R, as it happens) are meant to sometimes emit scalars, sometimes literal latex, sometimes tables to be formatted by orgs, and sometimes graphics. But all the non-graphics are at the moment being stuffed into (non-working) PDF files.

Following a discussion and suggested, but not-working solution at: https://emacs.stackexchange.com/questions/41618/org-modes-output-dir-and-file-ext-arguments-cause-all-output-to-be-saved-to

Thanks

alex

--------------2DA3F1CEAD35B6AFDD462158-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Babel - :export-dir and :file-ext arguments cause all blocks to emit files Date: Fri, 25 May 2018 01:13:26 +0200 Message-ID: <87wovsprzd.fsf@nicolasgoaziou.fr> References: <3ac2f42a-8ff2-1464-fa36-451e2ef0eacd@pressure.to> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41624) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fLzQN-00063R-6W for emacs-orgmode@gnu.org; Thu, 24 May 2018 19:13:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fLzQJ-0001HA-8Y for emacs-orgmode@gnu.org; Thu, 24 May 2018 19:13:35 -0400 Received: from relay6-d.mail.gandi.net ([217.70.183.198]:52361) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fLzQJ-0001Go-26 for emacs-orgmode@gnu.org; Thu, 24 May 2018 19:13:31 -0400 In-Reply-To: <3ac2f42a-8ff2-1464-fa36-451e2ef0eacd@pressure.to> (Alex Fenton's message of "Thu, 24 May 2018 23:50:30 +0200") 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: Alex Fenton Cc: emacs-orgmode@gnu.org Hello, Alex Fenton writes: > As far I understand it, |:output-dir| and |:file-ext| that were > intended to be used in the global document header, applying to all > blocks. > > However, it seems to mean that all blocks regardless of their :results > args then emit a file, and put their output as a [file:] link. It's > not clear from the docs why this happens. > > Am I missing something, or does this mean that these arguments are > useless unless a document happens only to emit graphics from blocks? > At the moment, the blocks (R, as it happens) are meant to sometimes > emit scalars, sometimes literal latex, sometimes tables to be > formatted by orgs, and sometimes graphics. But all the non-graphics > are at the moment being stuffed into (non-working) PDF files. > > Following a discussion and suggested, but not-working solution at: > https://emacs.stackexchange.com/questions/41618/org-modes-output-dir-and-file-ext-arguments-cause-all-output-to-be-saved-to I agree something is cheesy here. According to `org-babel-execute-src-block', if :file is set (it can also be forged from :file-ext and :output-dir according to `org-babel-generate-file-param'), results become the filename. Also, according to `org-babel-merge-params' both :file and :file-ext trump :results value, i.e., they automatically imply "file" in :results. and "results" in :exports. At this point, I'm not sure about :export, but I think it should be the other way for :results. IOW, :file and :file-ext should be taken into consideration only when :results contains "file". WDYT? Regards, -- Nicolas Goaziou 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 07:32:33 +0200 Message-ID: <9756a22c-8c00-0239-fbf1-be11717020e9@pressure.to> References: <3ac2f42a-8ff2-1464-fa36-451e2ef0eacd@pressure.to> <87wovsprzd.fsf@nicolasgoaziou.fr> 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]:41881) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fM5LD-0006Yf-RP for emacs-orgmode@gnu.org; Fri, 25 May 2018 01:32:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fM5LA-0001Ok-NG for emacs-orgmode@gnu.org; Fri, 25 May 2018 01:32:39 -0400 Received: from darwin.servwise.com ([31.193.138.136]:58980) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fM5LA-0001NT-D7 for emacs-orgmode@gnu.org; Fri, 25 May 2018 01:32:36 -0400 Received: from p578d3681.dip0.t-ipconnect.de ([87.141.54.129]:50178 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 1fM5L8-0002MO-4x for emacs-orgmode@gnu.org; Fri, 25 May 2018 05:32:34 +0000 In-Reply-To: <87wovsprzd.fsf@nicolasgoaziou.fr> 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" Cc: emacs-orgmode@gnu.org On 25/05/18 01:13, Nicolas Goaziou wrote: > Hello, > > Alex Fenton writes: > >> As far I understand it, |:output-dir| and |:file-ext| that were >> intended to be used in the global document header, applying to all >> blocks. >> >> However, it seems to mean that all blocks regardless of their :results >> args then emit a file, and put their output as a [file:] link. It's >> not clear from the docs why this happens. >> >> Am I missing something, or does this mean that these arguments are >> useless unless a document happens only to emit graphics from blocks? >> At the moment, the blocks (R, as it happens) are meant to sometimes >> emit scalars, sometimes literal latex, sometimes tables to be >> formatted by orgs, and sometimes graphics. But all the non-graphics >> are at the moment being stuffed into (non-working) PDF files. >> >> Following a discussion and suggested, but not-working solution at: >> https://emacs.stackexchange.com/questions/41618/org-modes-output-dir-and-file-ext-arguments-cause-all-output-to-be-saved-to > I agree something is cheesy here. > > According to `org-babel-execute-src-block', if :file is set (it can also > be forged from :file-ext and :output-dir according to > `org-babel-generate-file-param'), results become the filename. > > Also, according to `org-babel-merge-params' both :file and :file-ext > trump :results value, i.e., they automatically imply "file" in :results. > and "results" in :exports. > > At this point, I'm not sure about :export, but I think it should be the > other way for :results. IOW, :file and :file-ext should be taken into > consideration only when :results contains "file". > > WDYT? > > Regards, > From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Ecay Subject: Re: Babel - :export-dir and :file-ext arguments cause all blocks to emit files Date: Fri, 25 May 2018 14:47:59 +0100 Message-ID: <87fu2f7sog.fsf@gmail.com> References: <3ac2f42a-8ff2-1464-fa36-451e2ef0eacd@pressure.to> <87wovsprzd.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36257) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fMD4g-0004US-Sn for emacs-orgmode@gnu.org; Fri, 25 May 2018 09:48:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fMD4d-0001JF-QS for emacs-orgmode@gnu.org; Fri, 25 May 2018 09:48:06 -0400 Received: from mail-wr0-x22d.google.com ([2a00:1450:400c:c0c::22d]:45068) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fMD4d-0001Ii-JH for emacs-orgmode@gnu.org; Fri, 25 May 2018 09:48:03 -0400 Received: by mail-wr0-x22d.google.com with SMTP id w3-v6so9350840wrl.12 for ; Fri, 25 May 2018 06:48:03 -0700 (PDT) In-Reply-To: <87wovsprzd.fsf@nicolasgoaziou.fr> 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: Nicolas Goaziou , Alex Fenton Cc: emacs-orgmode@gnu.org Hi Nicolas, hi Alex, First of all, no issue arises with :output-dir alone. It can be specified as a global header arg without issue. The situation with :file is that it (currently and at all relevant times in the past AFAIK) implies :results file. That is because it would be a little strange if: #+begin_src R :file foo.pdf ... #+end_src did not result in the output going to foo.pdf 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. This perhaps could have been documented better when it was first introduced, and I see that subsequent changes in the manual have not made things clearer. 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. It=CA=BCs probably possible to write an org-lint check for the m= ost common broken case (where :file-ext is specified directly on a block, but :results file is not. This check would not catch a case where :file-ext was specified via a property for a buffer/subtree of blocks all of which are supposed to produce file results. Such a case should be rare, but it=CA=BCs not impossible.) I=CA=BCm still not 100% convinced that the brea= kage would be worth it, but I suppose I would incline towards that view. OTOH I do not think the proposed change makes sense for :file, because it would lead to a nonsensical situation in the case of the first block in this email. It never has made sense to specify :file by inheritance, so I don=CA=BCt think anything should change for that case. --=20 Aaron Ecay 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Ecay Subject: Re: Babel - :export-dir and :file-ext arguments cause all blocks to emit files Date: Sun, 27 May 2018 17:40:10 +0100 Message-ID: <87k1rpt5lh.fsf@gmail.com> References: <3ac2f42a-8ff2-1464-fa36-451e2ef0eacd@pressure.to> <87wovsprzd.fsf@nicolasgoaziou.fr> <87fu2f7sog.fsf@gmail.com> <6427e745-9ca4-2356-a262-ef257082a9ce@pressure.to> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51410) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fMyiO-0002zO-I7 for emacs-orgmode@gnu.org; Sun, 27 May 2018 12:40:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fMyiL-0002Kx-AK for emacs-orgmode@gnu.org; Sun, 27 May 2018 12:40:16 -0400 Received: from mail-wm0-x231.google.com ([2a00:1450:400c:c09::231]:51229) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fMyiL-0002K5-0L for emacs-orgmode@gnu.org; Sun, 27 May 2018 12:40:13 -0400 Received: by mail-wm0-x231.google.com with SMTP id j4-v6so26191504wme.1 for ; Sun, 27 May 2018 09:40:12 -0700 (PDT) In-Reply-To: <6427e745-9ca4-2356-a262-ef257082a9ce@pressure.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: Alex Fenton , emacs-orgmode@gnu.org Hi Alex, 2018ko maiatzak 25an, Alex Fenton-ek idatzi zuen: [...] > Now I understand how it was intended (a shortcut for people who are=20 > scrupulous about using #+NAME) it makes sense.=20 I=CA=BCve pushed commit 1643f70d3 to master which documents this behavior. > 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.). I agree it would be nice. You can have executable elisp in header arguments, so it is possible to do something like this (though ugly, since the same snippet has to be duplicated across every src block). One example of what I mean is at ; search for =E2=80=9Cby-backend=E2=80=9D in the page. [...] >=20 > You (all) are a better judge of what is a reasonable non-back-compatible= =20 > change. I=CA=BCm inclined not to make the change now, but (hopefully remember to) revisit it when Org 10 is imminent. Thanks for raising the issue, --=20 Aaron Ecay From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Babel - :export-dir and :file-ext arguments cause all blocks to emit files Date: Sun, 27 May 2018 21:54:53 +0200 Message-ID: <87tvqs3mcy.fsf@nicolasgoaziou.fr> References: <3ac2f42a-8ff2-1464-fa36-451e2ef0eacd@pressure.to> <87wovsprzd.fsf@nicolasgoaziou.fr> <87fu2f7sog.fsf@gmail.com> <6427e745-9ca4-2356-a262-ef257082a9ce@pressure.to> <87k1rpt5lh.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52161) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fN1kq-0005tZ-6n for emacs-orgmode@gnu.org; Sun, 27 May 2018 15:55:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fN1km-0002Em-VK for emacs-orgmode@gnu.org; Sun, 27 May 2018 15:55:00 -0400 Received: from relay10.mail.gandi.net ([217.70.178.230]:49701) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fN1km-0002Dn-P0 for emacs-orgmode@gnu.org; Sun, 27 May 2018 15:54:56 -0400 In-Reply-To: <87k1rpt5lh.fsf@gmail.com> (Aaron Ecay's message of "Sun, 27 May 2018 17:40:10 +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" To: Alex Fenton Cc: emacs-orgmode@gnu.org Hello, Aaron Ecay writes: > I=CA=BCve pushed commit 1643f70d3 to master which documents this behavior. Thank you. Please have a look at the consistency edits I made to it. > I=CA=BCm inclined not to make the change now, but (hopefully remember to) > revisit it when Org 10 is imminent. I agree now is clearly not the time for such a change. We could however try to make that right as soon as Org 9.2 is released. Regards, --=20 Nicolas Goaziou From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Ecay Subject: Re: Babel - :export-dir and :file-ext arguments cause all blocks to emit files Date: Sun, 27 May 2018 21:39:07 +0100 Message-ID: <87efhwu93o.fsf@gmail.com> References: <3ac2f42a-8ff2-1464-fa36-451e2ef0eacd@pressure.to> <87wovsprzd.fsf@nicolasgoaziou.fr> <87fu2f7sog.fsf@gmail.com> <6427e745-9ca4-2356-a262-ef257082a9ce@pressure.to> <87k1rpt5lh.fsf@gmail.com> <87tvqs3mcy.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59948) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fN2Re-0007be-Jt for emacs-orgmode@gnu.org; Sun, 27 May 2018 16:39:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fN2Ra-0005Q4-Mc for emacs-orgmode@gnu.org; Sun, 27 May 2018 16:39:14 -0400 Received: from mail-wr0-x22e.google.com ([2a00:1450:400c:c0c::22e]:42425) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fN2Ra-0005PV-GQ for emacs-orgmode@gnu.org; Sun, 27 May 2018 16:39:10 -0400 Received: by mail-wr0-x22e.google.com with SMTP id w10-v6so17084924wrk.9 for ; Sun, 27 May 2018 13:39:10 -0700 (PDT) In-Reply-To: <87tvqs3mcy.fsf@nicolasgoaziou.fr> 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: Nicolas Goaziou Cc: emacs-orgmode@gnu.org Hi Nicolas, 2018ko maiatzak 27an, Nicolas Goaziou-ek idatzi zuen: >=20 > Hello, >=20 > Aaron Ecay writes: >=20 >> I=CA=BCve pushed commit 1643f70d3 to master which documents this behavio= r. >=20 > Thank you. Please have a look at the consistency edits I made to it. Thanks very much. (As an aside: is org-footnote-auto-adjust TRT for the manual? It seems like it will lead to lots of churn every time a footnote is added or removed...) --=20 Aaron Ecay From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Babel - :export-dir and :file-ext arguments cause all blocks to emit files Date: Sun, 27 May 2018 22:50:04 +0200 Message-ID: <87efhw3jsz.fsf@nicolasgoaziou.fr> References: <3ac2f42a-8ff2-1464-fa36-451e2ef0eacd@pressure.to> <87wovsprzd.fsf@nicolasgoaziou.fr> <87fu2f7sog.fsf@gmail.com> <6427e745-9ca4-2356-a262-ef257082a9ce@pressure.to> <87k1rpt5lh.fsf@gmail.com> <87tvqs3mcy.fsf@nicolasgoaziou.fr> <87efhwu93o.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33281) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fN2cF-0001KI-Pz for emacs-orgmode@gnu.org; Sun, 27 May 2018 16:50:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fN2cC-0006pP-Hp for emacs-orgmode@gnu.org; Sun, 27 May 2018 16:50:11 -0400 Received: from relay10.mail.gandi.net ([217.70.178.230]:34679) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fN2cC-0006pK-Bv for emacs-orgmode@gnu.org; Sun, 27 May 2018 16:50:08 -0400 Received: from saiph (40-67.ipv4.commingeshautdebit.fr [185.131.40.67]) (Authenticated sender: admin@nicolasgoaziou.fr) by relay10.mail.gandi.net (Postfix) with ESMTPSA id 5BCB7240008 for ; Sun, 27 May 2018 22:50:05 +0200 (CEST) Received: from ngz by saiph with local (Exim 4.89) (envelope-from ) id 1fN2c8-0005Ki-Nq for emacs-orgmode@gnu.org; Sun, 27 May 2018 22:50:04 +0200 In-Reply-To: <87efhwu93o.fsf@gmail.com> (Aaron Ecay's message of "Sun, 27 May 2018 21:39:07 +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" To: emacs-orgmode@gnu.org Aaron Ecay writes: > (As an aside: is org-footnote-auto-adjust TRT for the manual? It seems > like it will lead to lots of churn every time a footnote is added or > removed...) This is a trade-off, indeed. It adds churn in diffs, but it's more natural to follow when editing or simply reading the Org file.