Nicolas Goaziou writes:
> Rasmus writes:
>
>> 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].
>
> The solution I gave you doesn't prompt anything.
Rasmus writes:
> 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].
The solution I gave you doesn't prompt anything.
> With the dependency specified in an
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.
Rasmus writes:
> 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 fi
Nicolas Goaziou writes:
> emacs --batch -Q -l conf.el --visit toexport.org -f org-latex-export-to-pdf
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
Rasmus writes:
> How to I generalize this to a emacs --batch call from a random org
> file?
What's wrong with
emacs --batch -Q -l conf.el --visit toexport.org -f org-latex-export-to-pdf
Regards,
Nicolas Goaziou writes:
>> No this has the same issue as the Makefile. "It's not as easy as latex".
>
> Setting up a publishing project is easy and well documented.
So is Makefile.
>> I want *one* coherent file with all the necessary instructions, that can
>> be edited in different program fro
Rasmus writes:
>> Can't you simply set-up a publishing project?
>
> No this has the same issue as the Makefile. "It's not as easy as latex".
Setting up a publishing project is easy and well documented.
> I want *one* coherent file with all the necessary instructions, that can
> be edited in di
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>>> 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 r
Hello,
Rasmus writes:
>> 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 ba
10 matches
Mail list logo
