Re: export_file_name problem with new exporter

[Alan Schmitt <alan.schmitt@polytechnique.org>]

Achim Gratz writes:

> Alan Schmitt writes:
>> In other words, I see three places of interest:
>> - where the org file is
>> - where export and compilation occurs
>> - where the final result is put
>>
>> Publishing lets us deal with the last one, but I don't think there is a
>> way to distinguish between the first two.
>
> Having a separate build directory would really need to be accompanied by
> a proper build system for all but the most simple tasks.  I think you
> can very well hand off the publishing to make or something like that.
> If you are only concerned about the litter from LaTeX, use a variant of
> "texi2pdf --tidy" instead of invoking pdftex directly.

Actually, I think this is the way to go. Having a "run this command
(asynchronously) after publishing" would be perfect. I need to look into
org-publish to see if this is not already present, and if it would be
difficult to add.

Alan