emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christophe Rhodes <csr21@cantab.net>
To: emacs-orgmode@gnu.org
Date: Thu, 20 Oct 2011 15:01:19 +0100	[thread overview]
Message-ID: <87fwin92z4.fsf@cantab.net> (raw)


When using #+SETUPFILE and exporting via LaTeX, the LATEX_CLASS_OPTIONS
provided in the included file are ignored.  With the following two files
in the same directory, doing C-c C-e L (org-export to a temporary LaTeX
buffer) produces a documentclass with class report (good, as expected)
and options [11pt] (not as expected).  Placing the LATEX_CLASS_OPTIONS
line in top.org produces the expected options.  I believe that the
reason is that LATEX_CLASS_OPTIONS is not handled within
org-infile-export-plist in org-exp.el.

--- top.org ---
#+TITLE: LaTeX Class Options
#+SETUPFILE: "include.org"

* Introduction
  Here is some text.
---   end   ---

--- include.org ---
#+LATEX_CLASS: report
#+LATEX_CLASS_OPTIONS: [a4paper,10pt]
---    end      ---

There may be similar keywords for LaTeX or other backends that are also
not handled which maybe should be; this one is the one I noticed because
I tried to use it.

Best wishes,


             reply	other threads:[~2011-10-20 14:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-20 14:01 Christophe Rhodes [this message]
2011-10-26 15:14 ` [patch] Re: LATEX_CLASS_OPTIONS in SETUPFILE Christophe Rhodes
2011-10-26 17:27   ` Bastien

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:

  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=87fwin92z4.fsf@cantab.net \
    --to=csr21@cantab.net \
    --cc=emacs-orgmode@gnu.org \


* 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).