emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: External compilation
Date: Thu, 19 Feb 2015 12:35:48 +0100	[thread overview]
Message-ID: <87wq3e5e23.fsf@gmx.us> (raw)

Hi,

I want to translate some documents to pdf.  I'm currently doing it with
something like this

    OX-FUN    = emacs --batch --no-init-file --load conf.el $1 --funcall $2 --kill
    OX-LATEX  = $(call OX-FUN, $1, org-latex-export-to-pdf)

But this is very limiting (I am told) as it require me to maintain a
Makefile.  It's not as easy as latex.

I can move the call to  Emacs as file variable s.t.

    # Local Variables:
    # eval:  (unless (or user-init-file (window-system)) (load-file "conf.el"))
    # End:

And export by calling:

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

But this is kind of annoying as it disturbs opening the file

I tried to port my config to conf.org and let babel handle it, but
conf.org also defines the document class so I never get to the babel
evaluation stage.

Has anybody come up with a better method?

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.

—Rasmus

-- 
This message is brought to you by the department of redundant departments

next             reply	other threads:[~2015-02-19 11:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19 11:35 Rasmus [this message]
2015-02-19 14:16 ` External compilation Sebastien Vauban
2015-02-19 14:47   ` Rasmus
2015-02-19 14:50     ` Sebastien Vauban
2015-02-20 12:07 ` [ox, patch] external compilation (was: External compilation) Rasmus
2015-02-20 16:10   ` [ox, patch] external compilation Nicolas Goaziou
2015-02-20 16:24     ` Rasmus
2015-02-20 17:34       ` Nicolas Goaziou
2015-02-20 18:21         ` Rasmus
2015-02-20 19:01           ` Nicolas Goaziou
2015-02-20 19:38             ` Rasmus
2015-02-21  9:35               ` Nicolas Goaziou
2015-02-21 11:35                 ` Rasmus
2015-02-21 12:59                   ` Nicolas Goaziou
2015-02-21 13:23                     ` Rasmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wq3e5e23.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).