emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Aaron Ecay <aaronecay@gmail.com>
To: Alex Fenton <alex@pressure.to>, emacs-orgmode@gnu.org
Subject: Re: Babel - :export-dir and :file-ext arguments cause all blocks to emit files
Date: Sun, 27 May 2018 17:40:10 +0100	[thread overview]
Message-ID: <87k1rpt5lh.fsf@gmail.com> (raw)
In-Reply-To: <6427e745-9ca4-2356-a262-ef257082a9ce@pressure.to>

Hi Alex,

2018ko maiatzak 25an, Alex Fenton-ek idatzi zuen:

[...]


> Now I understand how it was intended (a shortcut for people who are 
> scrupulous about using #+NAME) it makes sense. 

Iʼve 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
<https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-LaTeX.html>;
search for “by-backend” in the page.


[...]

> 
> You (all) are a better judge of what is a reasonable non-back-compatible 
> change.

Iʼm inclined not to make the change now, but (hopefully remember to)
revisit it when Org 10 is imminent.

Thanks for raising the issue,

-- 
Aaron Ecay

  reply	other threads:[~2018-05-27 16:40 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
2018-05-27 16:40       ` Aaron Ecay [this message]
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=87k1rpt5lh.fsf@gmail.com \
    --to=aaronecay@gmail.com \
    --cc=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).