Rasmus <rasmus@gmx.us> writes:

> I can move the call to  Emacs as file variable s.t.
>
>     # Local Variables:
>     # eval:  (unless (or user-init-file (window-system)) (load-file "conf.el"))
>     # End:

A much better variable to check is `noninteractive', cf
(info "(elisp) Batch mode").

> Ideally, what I would like would be to specify a per-file/project init
> file.  Sort of like org-export-async-init-file, but as part of
> org-export-options-alist to get the "init.el-dependency" inside the
> Org-file.  It would be read when Org exports async or via batch.

This patch moves org-export-async-init-file to org-export-options-alist
and introduces #+INIT for setting it in a file.

It also automatically "switches" to async export if running Emacs in
batch.  I don't know if this is a good idea!  E.g. I guess it would starts
a new Emacs process from a Emacs batch process...

WDYT?  Would something like this be appropriate?

—Rasmus

-- 
One thing that is clear: it's all down hill from here