all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Fenton <alex@pressure.to>
To: emacs-orgmode@gnu.org
Subject: Babel - :export-dir and :file-ext arguments cause all blocks to emit files
Date: Thu, 24 May 2018 23:50:30 +0200	[thread overview]
Message-ID: <3ac2f42a-8ff2-1464-fa36-451e2ef0eacd@pressure.to> (raw)

[-- Attachment #1: Type: text/plain, Size: 939 bytes --]

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


[-- Attachment #2: Type: text/html, Size: 1651 bytes --]

             reply	other threads:[~2018-05-24 22:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24 21:50 Alex Fenton [this message]
2018-05-24 23:13 ` Babel - :export-dir and :file-ext arguments cause all blocks to emit files 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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ac2f42a-8ff2-1464-fa36-451e2ef0eacd@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.