From: suvayu ali <fatkasuvayu@gmail.com>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: [BUG] LATEX_CLASS_OPTIONS not working
Date: Tue, 6 Mar 2012 03:13:57 +0100 [thread overview]
Message-ID: <CAMXnza0X4ana7+QYPx1tz3adjW8DpCmpV6RALrOqzPpDNrcCgg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
Hi,
I think there is a regression bug in latex export. The
#+LATEX_CLASS_OPTIONS: a4paper
directive is supposed to generate the following latex code:
\documentclass{a4paper,article}
Instead it generates:
\documentclassa4paper{article}
A minimal example is attached.
Thanks,
--
Suvayu
Open source is the future. It sets us free.
[-- Attachment #2: bug.org --]
[-- Type: text/x-tex, Size: 334 bytes --]
#+LATEX_CLASS: article
#+LATEX_CLASS_OPTIONS: a4paper
#+LATEX_HEADER: \setmainfont{Linux Libertine}
* Top heading
** Meeting
:PROPERTIES:
:LaTeX_CLASS: article
:EXPORT_FILE_NAME: report.pdf
:EXPORT_TITLE: Report
:EXPORT_OPTIONS: H:1 num:nil toc:nil ^:{}
:END:
*** Things
+ Some item
+ Item 2
+ Last item
* Last heading
[-- Attachment #3: bug.tex --]
[-- Type: application/x-tex, Size: 928 bytes --]
next prev reply other threads:[~2012-03-06 2:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 22:02 Problem with choosing mode while editing blocks with C-c ' suvayu ali
2012-03-13 22:43 ` Nick Dokos
2012-03-13 23:04 ` Thorsten
2012-03-14 0:14 ` Nick Dokos
2012-03-14 7:07 ` Thorsten
[not found] ` <quintfall@googlemail.com>
2012-03-14 0:34 ` Nick Dokos
[not found] ` <fatkasuvayu@gmail.com>
2012-03-06 2:13 ` suvayu ali [this message]
2012-03-06 2:42 ` [BUG] LATEX_CLASS_OPTIONS not working Nick Dokos
2012-03-06 15:11 ` suvayu ali
2012-03-07 22:20 ` Nick Dokos
2012-03-08 0:43 ` suvayu ali
2012-03-14 2:32 ` Problem with choosing mode while editing blocks with C-c ' suvayu ali
2012-03-14 2:59 ` Nick Dokos
2012-03-14 3:11 ` Nick Dokos
2012-03-14 8:41 ` suvayu ali
2012-03-14 9:03 ` Suvayu Ali
2012-03-14 13:50 ` Nick Dokos
2012-03-20 2:04 ` 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:
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=CAMXnza0X4ana7+QYPx1tz3adjW8DpCmpV6RALrOqzPpDNrcCgg@mail.gmail.com \
--to=fatkasuvayu@gmail.com \
--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 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).