From: Suvayu Ali <email@example.com>
Subject: Re: Macros in included file not expanded in batch export
Date: Tue, 15 Jul 2014 08:54:22 +0200 [thread overview]
Message-ID: <20140715065422.GD2413@chitra.no-ip.org> (raw)
On Mon, Jul 14, 2014 at 10:50:53PM -0400, Nick Dokos wrote:
> Suvayu Ali <firstname.lastname@example.org> writes:
> > Hi,
> > I am trying to export to LaTeX in batch mode, but it seems the exporter
> > ignores macros defined in included files when exporting in batch mode.
> > I tried to export like this:
> > $ emacs --eval "(require 'ox-latex)" include-test.org \
> > --eval '(org-LaTeX-export-to-latex nil nil nil t)' -f kill-emacs
> > $ emacs --batch --eval "(require 'ox-latex)" include-test.org \
> > --eval '(org-LaTeX-export-to-latex nil nil nil t)'
> > The first one exports correctly, the second doesn't. The org files, and
> > the good and bad exported TeX files are attached.
> I haven't tried it but --batch implies -q, so it may be that the second
> form is missing something essential from your init file - maybe?
Indeed! I wasn't aware --batch implies -q, I had checked the man page
before using it, but it isn't there. Probably it is hidden somewhere in
Although, I can't think of what config it must be. As far as I recall I
do not have anything related to include files or macro expansion.
Anyway, thank you :).
Open source is the future. It sets us free.
next prev parent reply other threads:[~2014-07-15 6:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 22:24 Macros in included file not expanded in batch export Suvayu Ali
2014-07-15 2:50 ` Nick Dokos
2014-07-15 6:54 ` Suvayu Ali [this message]
2014-07-15 10:49 ` Nick Dokos
2014-07-28 17:59 ` Fabrice Niessen
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
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).