Hi,
I fixed this bug.
Christian Moe writes:
> On 3/8/12 7:38 AM, A. Major wrote:
>> 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.
>
> Yes, that's why I said "this part of the problem".
>
On 3/8/12 7:38 AM, A. Major wrote:
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.
Yes, that's why I said "this part of the problem".
Combining BIND and the "dir" PROPERTY, I can get HTML a
Christian Moe christianmoe.com> writes:
>
>
> >>> On Wed, 7 Mar 2012 12:38:48 + (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 directo
On Wed, 7 Mar 2012 12:38:48 + (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
>> On Wed, 7 Mar 2012 12:38:48 + (UTC), A Major said:
> Hi, 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-directo
Hi,
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 f
