Re: export_file_name problem with new exporter

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

Nicolas Goaziou writes:

> There is no #+EXPORT_FILE_NAME: keyword. But there is
> an :EXPORT_FILE_NAME: node-property for subtree export. There could be
> a #+FILE_NAME: keyword (much like :EXPORT_AUTHOR: and #+AUTHOR). Though,
> it is too dangerous to my liking.
>
> For example, publishing expects the output file to be generated in the
> working directory. Using a different export path per file could lead to
> much confusion.
>
> Hence I'd rather not implement it.

I understand it. What I actually would like is to be able to specify a
different "working directory". Right now it defaults to the directory
where the org file is, but it's often not satisfactory (especially when
compilation creates additional files). Would this be difficult to add?

Thanks,

Alan