2

Context When exporting Org-Mode documents to LaTeX it is possible to specifcy additional LaTeX header commands:

#+LaTeX_HEADER: \subtitle{This is a subtitle}

Using org-publish it is possible to specify some more advanced exporting options.

(setq org-publish-project-alist
  '(
    ("text"
     :base-directory "~/somedir"
     :base-extension "org"
     :publishing-directory "~/somedir"
     :preparation-function somepreparationfunction
     :completion-function  somecompletionfunction
     :publishing-function org-latex-publish-to-pdf
     :include ("somedocument.org")
     :exclude "\\.org$"
     :latex-class "scrartcl"
     :headline-levels 5
     :with-toc nil
     :select-tags ("Text")
     )
    ))

As far as I can see it's usually possible to specify each options either in the Org-Mode document or in the org-publish-project-alist data structure. But :latex-header does not seem to be recognized altough it is specified in lisp/ox-latex.el (HEAD).

Question How do I specify additional LaTeX header commands in the org-publish-project-alist, i.e. being able to specify them seperately in the case of multiple publishing projects for the same document?

  • 1
    What if you try :setupfile and put additional header in that file? – wvxvw Sep 15 '15 at 17:24
  • 1
    I thought using :latex-header would be possible in a custom publish function, but on closer investigation it doesn't look that way. @wvxvw's solution seems to be the only way to do this. – suvayu Sep 22 '15 at 20:21
  • @wvxvw I'm afraid that :setupfile "~/setup-pipeline.org" is not supported in org-publish-project-alist. #+SETUPFILE: setup-pipeline.org works. Today I've found a related question: emacs.stackexchange.com/questions/7438 – Christoph Sep 30 '15 at 13:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.