emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: [PATCH] Add example demonstrating LaTeX_CLASS_OPTIONS
Date: Thu, 8 Mar 2012 01:41:27 +0100	[thread overview]
Message-ID: <CAMXnza2cUPE7t_D+=VCZhyE0uFgiZKsji=L5peyOnBfJccBKJw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 203 bytes --]


This is adds a small example to better illustrate the use of
LaTeX_CLASS_OPTIONS. Thanks to Nick for encouraging me to submit this.



Open source is the future. It sets us free.

[-- Attachment #2: 0001-Add-example-demonstrating-LaTeX_CLASS_OPTIONS.patch --]
[-- Type: text/x-patch, Size: 1877 bytes --]

From 1e8dc6e253ba72a1574dc7fb5f91028f68f01241 Mon Sep 17 00:00:00 2001
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Date: Thu, 8 Mar 2012 01:31:05 +0100
Subject: [PATCH] Add example demonstrating LaTeX_CLASS_OPTIONS

* org.texi (Header and sectioning): Add example demonstrating how to use

 doc/org.texi |   21 ++++++++++++++++-----
 1 files changed, 16 insertions(+), 5 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index 33ffe28..84d3102 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -10361,11 +10361,22 @@ @subsection Header and sectioning structure
 @code{org-export-latex-default-packages-alist} and
 @code{org-export-latex-packages-alist} are spliced.}, and allows you to
 define the sectioning structure for each class.  You can also define your own
-classes there.  @code{#+LaTeX_CLASS_OPTIONS} or a @code{LaTeX_CLASS_OPTIONS}
-property can specify the options for the @code{\documentclass} macro.  You
-can also use @code{#+LaTeX_HEADER: \usepackage@{xyz@}} to add lines to the
-header.  See the docstring of @code{org-export-latex-classes} for more
+classes there.  @code{#+LaTeX_CLASS_OPTIONS} or a @code{:LaTeX_CLASS_OPTIONS:}
+property can specify the options for the @code{\documentclass} macro.  The
+options to documentclass have to be provided, as expected by @LaTeX{}, within
+square brackets.  You can also use @code{#+LaTeX_HEADER: \usepackage@{xyz@}}
+to add lines to the header.  See the docstring of
+@code{org-export-latex-classes} for more information.  An example is shown
+#+LaTeX_CLASS: article
+#+LaTeX_CLASS_OPTIONS: [a4paper]
+#+LaTeX_HEADER: \usepackage{xyz}
+* Headline 1
+  some text
+@end example
 @node Quoting @LaTeX{} code, Tables in @LaTeX{} export, Header and sectioning, @LaTeX{} and PDF export
 @subsection Quoting @LaTeX{} code

             reply	other threads:[~2012-03-08  0:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-08  0:41 suvayu ali [this message]
2012-03-08 12:18 ` [PATCH] Add example demonstrating LaTeX_CLASS_OPTIONS suvayu ali
2012-03-08 12:45   ` 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='CAMXnza2cUPE7t_D+=VCZhyE0uFgiZKsji=L5peyOnBfJccBKJw@mail.gmail.com' \
    --to=fatkasuvayu+linux@gmail.com \
    --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).