Nicolas Goaziou <m...@nicolasgoaziou.fr> writes: > Hello, > > Rasmus <ras...@gmx.us> 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 batch. >> >> This patch moves org-export-async-init-file to org-export-options-alist >> and introduces #+INIT for setting it in a file. >>SW >> 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? > > 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". I want *one* coherent file with all the necessary instructions, that can be edited in different program from Emacs, and be easily compiled. E.g. I wrote syntax highlight for Org in texworks, but I also want to make the "green button" work easily as latex without too many ugly hacks. A makefile or a ox-project is great for the pros. Unfortunately not everyone is... Makefiles and projects is the tool better for multi-file projects. —Rasmus -- A clever person solves a problem. A wise person avoids it
