* Thomas S. Dye <t...@tsdye.com> wrote: > Karl Voit <devn...@karl-voit.at> writes: > >> https://github.com/novoid/orgmode-ACM-template >> > Hi Karl,
Hi! > IIUC, you'd like to configure Org-mode to export a LaTeX file that is > functionally equivalent to sigproc-sp.tex. Yes. If it is possible, I want to have an equivalent PDF and an equivalent TeX as well. > If this is the case, it might be best to change the name of > orgmode.org to sigproc-sp.org or something similar. It has to be something similar. Otherwise the sigproc-sp.tex gets overwritten by the exporter. > If the goal is to support both exporters, perhaps > sigproc-sp-old.org and sigproc-sp-new.org? Good idea. I'll change it. > In my view, it is best to encapsulate as much of the Org-mode > configuration as possible in an init.el file. That way, users of the > Org-mode template can launch with emacs -Q etc. and not have to worry > about their own customizations that might conflict with the > configuration. An example is here: https://github.com/tsdye/LKFS.git. > Perhaps two initialization files would be needed: init-new.el and > init-old.el? I was hoping that it is possible to encapsulate everything in the Org-mode file instead. «#+name: setup» looked very promising to me for that purpose ... (but so far I could not achieve any impact with it) >> With the new exporter, I was not able to compile the Org-mode file >> at all. Since the old exporter had troubles using this >> "per-file-class" I do have a feeling that this might be the cause >> for the error message with the new exporter too. > > I'll have a look at this and send you patches off list. Great! -- Karl Voit
