Re: BUG(?): #+BINDing org-export-publishing-directory only affects HTML output, not PDF or Babel results

[A. Major <andras.g.major@gmail.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? :)