Re: [O] [ox, patch] external compilation

[Rasmus]

Hi,

>> That it hardcodes conf.el.  So it doesn't toexport1.org which depends on
>> config/conf.el.  I want to specify the dependency in in toexport.org
>> explicitly so that
>>
>>      emacs --batch -Q --visit toexport.org -f org-latex-export-to-pdf
>>
>> generally works with custom-config files.  Again, think about supporting a
>> Org from a editor where you just have "one button".
>
> Then
>
>   # Local Variables:
>   # org-export-async-init-file: "config/config.el"
>   # End:
>
> at the end of your file and
>
>   emacs --batch -Q --eval="(setq enable-local-variables :all)" --visit
> toexport.org --eval="(org-export-latex-to-pdf t)"

That's more or less what I do cf. the first post, namely

# Local Variables:
# eval:  (unless noninteractive (load-file "org-conf.el"))
# End:

[Which gives me the annoying prompt].

I call Emacsfor like this. For some reason I had to explicitly require
'ox, maybe just me doing a mistake.

emacs --batch --no-init-file --eval="(progn (setq enable-local-eval t) (require 
'ox-latex))" $1 --funcall=org-latex-export-to-pdf

The whole point is that I would like to cut it down to:

    emacs --batch --no-init-file $1 --funcall=org-latex-export-to-pdf

With the dependency specified in an #+INIT or #+PREAMBLE or #+LISP-SETUP
or whatever. For the sake of making ox export for arbitrary $1 " as easy
as latex".  (Even better would be a dedicated binary: "ox --latex $1").

I don't know if it's a security issue, and if you don't see a benefit from
the above, I won't push further.

—Rasmus

-- 
Slowly unravels in a ball of yarn and the devil collects it