From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: [bug] export to latex doesn't process #+include files fully
Date: Fri, 19 Nov 2010 13:17:53 +0000 [thread overview]
Message-ID: <87y68p1mgu.fsf@ucl.ac.uk> (raw)
Hello,
should the latex export take into account any settings in an included
file? Although #+include works in the sense that any text in that file
is included in an export, the settings (e.g. #+latex_header:) are
ignored on export.
This simple example:
--8<---------------cut here---------------start------------->8---
# -*- coding: utf-8; -*-
#+TITLE: examplebug.org
#+AUTHOR: Eric S Fraga
#+EMAIL: e.fraga@ucl.ac.uk
#+DESCRIPTION:
#+KEYWORDS:
#+LANGUAGE: en
#+OPTIONS: H:3 num:t toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t
#+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc
#+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport
#+LINK_UP:
#+LINK_HOME:
#+XSLT:
#+include: "preamble.org"
* include bug
Including another org file doesn't seem to include all of the
material upon export. This was written by \esf{}.
--8<---------------cut here---------------end--------------->8---
with =preamble.org= having a single line:
--8<---------------cut here---------------start------------->8---
#+latex_header: \newcommand{\esf}{\fbox{ESF}}
--8<---------------cut here---------------end--------------->8---
illustrates this.
I know that the file is being /included/ as any text put in preamble.org
appears in the resulting .tex file. However, the latex_header commands
are not being passed through. Should they be or is this a design
decision?
Thanks,
eric
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 23.2.1
: using Org-mode version 7.3 (release_7.3.93.g451ac)
reply other threads:[~2010-11-19 13:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y68p1mgu.fsf@ucl.ac.uk \
--to=ucecesf@ucl.ac.uk \
--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
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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.