From: A. Major <email@example.com>
Subject: BUG(?): #+BINDing org-export-publishing-directory only affects HTML output, not PDF or Babel results
Date: Wed, 7 Mar 2012 12:38:48 +0000 (UTC) [thread overview]
Message-ID: <loom.20120307T133057firstname.lastname@example.org> (raw)
I'm trying to set up my .org file such that export commands create all
results in a certain directory rather than the directory containing
the .org file. So I've added the option
#+BIND: org-export-publishing-directory "/tmp/export-test"
at the beginning of the file, which seems to work fine for a simple
test file with HTML export.
If I try to export the .org file as a PDF document, however, the
result still resides in the directory containing the .org file --
which isn't what I want and is also counterintuitive given the name of
the variable set in the BIND option.
Even worse, if the .org file uses Babel to create files (say, in PNG
format) as a result (via ditaa, graphviz, etc.), then these files end
up in the directory containing the .org file, not in /tmp/export-test,
where the HTML file is placed. This leaves the HTML output completely
Is there a proper way of doing this (short of "publishing", which
isn't what I want because I find it too complex in my case), and am I
doing something very wrong here?
next reply other threads:[~2012-03-07 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 12:38 A. Major [this message]
2012-03-07 16:10 ` BUG(?): #+BINDing org-export-publishing-directory only affects HTML output, not PDF or Babel results Myles English
2012-03-07 17:30 ` Christian Moe
2012-03-08 6:38 ` A. Major
2012-03-08 20:09 ` Christian Moe
2012-03-23 13:00 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).