emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: A. Major <andras.g.major@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: BUG(?): #+BINDing org-export-publishing-directory only affects HTML output, not PDF or Babel results
Date: Thu, 8 Mar 2012 06:38:02 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120308T073456-970@post.gmane.org> (raw)
In-Reply-To: 4F579B2A.6030104@christianmoe.com

Christian Moe <mail <at> christianmoe.com> writes:

> >>> On Wed, 7 Mar 2012 12:38:48 +0000 (UTC), A Major said:
> >
> >    >  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 broken.
> IIUC, this part of the problem should be easy to solve with the :dir 
> header argument? You can set it once for the whole file with:
> #+PROPERTY: dir /tmp/export-test
> Yours,
> Christian

Thanks, but the "dir" PROPERTY appears to affect the target directory for
babel's results, neither the HTML nor the PDF output are influenced that way.

Combining BIND and the "dir" PROPERTY, I can get HTML and babel files in the
right place, but not the PDF.

Any other suggestions? :)

  reply	other threads:[~2012-03-08  6:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07 12:38 BUG(?): #+BINDing org-export-publishing-directory only affects HTML output, not PDF or Babel results A. Major
2012-03-07 16:10 ` Myles English
2012-03-07 17:30   ` Christian Moe
2012-03-08  6:38     ` A. Major [this message]
2012-03-08 20:09       ` Christian Moe
2012-03-23 13:00         ` Bastien

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:

  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=loom.20120308T073456-970@post.gmane.org \
    --to=andras.g.major@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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).