From: Nick Dokos <nicholas.dokos@hp.com>
To: avdi@avdi.org
Cc: nicholas.dokos@hp.com, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Missing Introduction and About sections in LaTeX export
Date: Wed, 27 Apr 2011 17:41:26 -0400 [thread overview]
Message-ID: <5291.1303940486@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from Avdi Grimm <groups@inbox.avdi.org> of "Wed, 27 Apr 2011 16:57:11 EDT." <BANLkTintk1-+dWGABbLwy7S1g19k-OptfA@mail.gmail.com>
Avdi Grimm <groups@inbox.avdi.org> wrote:
> I have an Org document I'm exporting to PDF through LaTeX using the
> "report" class.
>
> The two first top-level sections in the document, titled "About" and
> "Introduction", are completely missing from the generated .tex and
> PDF. The exported files start on the third section.
>
Can't reproduce this:
--8<---------------cut here---------------start------------->8---
#+latex_class: report
* About
foo
* Introduction
bar
* First real section
baz
--8<---------------cut here---------------end--------------->8---
when exported to latex it gives:
,----
| ...
| \part{About}
| \label{sec-1}
|
|
| foo
| \part{Introduction}
| \label{sec-2}
|
|
| bar
| \part{First real section}
| \label{sec-3}
|
|
| baz
`----
and all three appear in the TOC.
Org-mode version 7.5 (release_7.5.181.g66caf)
GNU Emacs 24.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.22.0) of 2011-04-13
> Coincidentally(?) those are the "front matter" sections which I don't
> want included in the contents. However, I have done nothing to mark
> them as such. They have no classes or properties. As far as I can tell
> there is nothing making them different from other sections.
>
> Any ideas why they might be elided by the LaTeX exporter in Org 7.5?
>
> Follow-up: assuming I can get them to export at all, how can I mark
> *just* those two headings to be exported using the "starred" form so
> that they are not included in the chapter numbering?
>
Just star them by hand in the tex file after exporting for the last
time: it'll take two seconds. You may be able to do it from Org by
writing a custom function (C-h v org-export-latex-classes <RET> for
details) but I suspect that the effort is just not worth it.
Nick
next prev parent reply other threads:[~2011-04-27 21:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 20:57 Missing Introduction and About sections in LaTeX export Avdi Grimm
2011-04-27 22:21 ` Avdi Grimm
2011-04-28 11:06 ` Eric S Fraga
[not found] ` <groups@inbox.avdi.org>
2011-04-27 21:41 ` Nick Dokos [this message]
2011-04-27 21:47 ` Avdi Grimm
2011-04-27 22:23 ` Nick Dokos
2011-04-28 7:55 ` Sébastien Vauban
2011-04-28 11:36 ` Nick Dokos
2011-05-01 19:04 ` Dumbquotes in exported source listings Nick Dokos
-- strict thread matches above, loose matches on Subject: below --
2011-04-30 23:39 Avdi Grimm
2011-05-01 3:13 ` Ben Finney
2011-05-01 16:41 ` Avdi Grimm
2011-05-01 19:08 ` Nick Dokos
2011-05-01 20:26 ` Sébastien Vauban
2011-05-01 21:31 ` Nick Dokos
2011-05-01 21:40 ` Ben Finney
2011-05-01 21:27 ` Ben Finney
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=5291.1303940486@alphaville.americas.hpqcorp.net \
--to=nicholas.dokos@hp.com \
--cc=avdi@avdi.org \
--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).