From: Nick Dokos <nicholas.dokos@hp.com>
To: Michael Hannon <jm_hannon@yahoo.com>
Cc: nicholas.dokos@hp.com, Org-Mode List <emacs-orgmode@gnu.org>
Subject: Re: Include TOC in PDF export?
Date: Fri, 02 Mar 2012 18:21:55 -0500 [thread overview]
Message-ID: <8315.1330730515@alphaville> (raw)
In-Reply-To: Message from Michael Hannon <jm_hannon@yahoo.com> of "Fri\, 02 Mar 2012 14\:32\:44 PST." <1330727564.64930.YahooMailNeo@web161903.mail.bf1.yahoo.com>
Michael Hannon <jm_hannon@yahoo.com> wrote:
> Greetings. I'm exporting a document to both HTML and PDF. In the
> HTML version, I get a table of contents. In the PDF version, I do NOT
> get a table of contents. The appended text illustrates the problem.
> I'd like to get the TOC in both.
>
num:nil causes unnumbered sections in latex (\section*{...}) which are
not entered into the .toc file (that's a latex limitation, not an
org-mode one), so the latex exporter wants both num: and toc: to be
enabled before it produces a table of contents.
I think the only way to get a TOC is to set num:t. You can probably
rewrite a chunk of latex code so that unnumbered sections etc end up in
the .toc file, but I think it would be a fairly major undertaking.
Nick
>
> I'm running:
>
> Org-mode version 7.8.03 (release_7.8.03.324.gc4b233)
>
> in Fedora 16, 64-bit.
>
> What am I missing?
>
> Thanks,
>
> -- Mike
>
>
>
> #+TITLE:
> #+OPTIONS: num:nil ^:{} toc:t
>
> * Tale of Two Cities
>
> *It was the best of times, it was the worst of times*
>
> It was the best of times, it was the worst of times, it was the age of
> wisdom, it was the age of foolishness, it was the epoch of belief, it
> was the epoch of incredulity, it was the season of Light, it was the
> season of Darkness, it was the spring of hope, it was the winter of
> despair, we had everything before us, we had nothing before us, we
> were all going direct to heaven, we were all going direct the other
> way - in short, the period was so far like the present period, that
> some of its noisiest authorities insisted on its being received, for
> good or for evil, in the superlative degree of comparison only.
>
> * David Copperfield
>
> *Barkis is willin*
>
> As he repudiated this suggestion, however, with a jerk of his head,
> and once more confirmed his previous request by saying, with profound
> gravity, 'Barkis is willin'. That's the message,' I readily undertook
> its transmission. While I was waiting for the coach in the hotel at
> Yarmouth that very afternoon, I procured a sheet of paper and an
> inkstand, and wrote a note to Peggotty, which ran thus: 'My dear
> Peggotty. I have come here safe. Barkis is willing. My love to
> mama. Yours affectionately. P.S. He says he particularly wants you to
> know - BARKIS IS WILLING.'
>
next prev parent reply other threads:[~2012-03-02 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 22:32 Include TOC in PDF export? Michael Hannon
2012-03-02 23:21 ` Nick Dokos [this message]
2012-03-02 23:39 ` Nick Dokos
2012-03-02 23:44 ` Michael Hannon
2012-03-03 0:23 ` suvayu ali
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=8315.1330730515@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=jm_hannon@yahoo.com \
/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).