From: Alex Fenton <alex@pressure.to>
To: emacs-orgmode@gnu.org
Subject: Re: Babel - :export-dir and :file-ext arguments cause all blocks to emit files
Date: Fri, 25 May 2018 21:52:02 +0200 [thread overview]
Message-ID: <6427e745-9ca4-2356-a262-ef257082a9ce@pressure.to> (raw)
In-Reply-To: <87fu2f7sog.fsf@gmail.com>
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
next prev parent reply other threads:[~2018-05-25 19:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 21:50 Babel - :export-dir and :file-ext arguments cause all blocks to emit files Alex Fenton
2018-05-24 23:13 ` Nicolas Goaziou
2018-05-25 5:32 ` Alex Fenton
2018-05-25 13:47 ` Aaron Ecay
2018-05-25 19:52 ` Alex Fenton [this message]
2018-05-27 16:40 ` Aaron Ecay
2018-05-27 19:54 ` Nicolas Goaziou
2018-05-27 20:39 ` Aaron Ecay
2018-05-27 20:50 ` Nicolas Goaziou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6427e745-9ca4-2356-a262-ef257082a9ce@pressure.to \
--to=alex@pressure.to \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).