From: Vikas Rawal <email@example.com>
To: emacs-orgmode <firstname.lastname@example.org>
Subject: Heading numbering in latex export
Date: Thu, 27 Sep 2012 12:15:27 +0530 [thread overview]
Message-ID: <20120927064527.GA17906@panahar> (raw)
I am writing a research paper using orgmode. The org file contains the
text of the paper and R source code for generating a graph and some
tables. The paper is still incomplete.
When I try to export the file to pdf via latex, I face a strange
problem. When I export the file first time after opening it, the
graph does not appear. When I do it again, the graph appears fine but
Section numbers are messed up. The main sections are now numbered 0.1,
0.2 etc while the sub-sections are not numbered at all.
In my header, I have:
#+OPTIONS: H:3 toc:nil
I have changed the value of H but it has no effect.
Can somebody please explain what might be wrong.
I am using org-version 7.9.1.
next reply other threads:[~2012-09-27 6:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 6:45 Vikas Rawal [this message]
2012-09-27 7:36 ` Bastien
2012-09-27 15:37 ` Vikas Rawal
2012-09-27 22:33 ` Bastien
2012-09-27 22:29 ` Vikas Rawal
2012-09-28 8:06 ` Suvayu Ali
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).