[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] different toc levels per headline?
From: |
Carsten Dominik |
Subject: |
Re: [O] different toc levels per headline? |
Date: |
Thu, 26 Sep 2013 13:15:56 +0200 |
Hi Adam,
EXPORT_OPTIONS are for the special case that you only export that specific
subtree, by restricting the export to a tree using C-s in the dispatcher. They
do not modify the behavior of a tree in a larger export of the document, and
they also should not do so IMO. Generating a single document should follow one
set of rules, not many.
- Carsten
On 26.9.2013, at 13:01, Adam Spiers <address@hidden> wrote:
> Hi all,
>
> If I have something like:
>
> #+OPTIONS: toc:1
>
> * h1 no options
> *** h2
> ***** h3
> * h1 toc:2
> :PROPERTIES:
> :EXPORT_OPTIONS: toc:2
> :END:
> *** h2
> ***** h3
> * h1 toc:3
> :PROPERTIES:
> :EXPORT_OPTIONS: toc:3
> :END:
> *** h2
> ***** h3
>
> I would expect a ToC which looks like:
>
> Table of Contents
> _________________
>
> 1 h1 no options
> 2 h1 toc:1
> .. 2.1 h2
> 3 h1 toc:2
> .. 3.1 h2
> ..... 3.1.1 h3
>
> In otherwise, I would expect the EXPORT_OPTIONS in the subtrees to
> override the file-wide setting for `toc'. This expectation is based
> on what the manual says:
>
> Export options can be set: globally with variables; for an
> individual file by making variables buffer-local with in-buffer
> settings (*note In-buffer settings::), by setting individual
> keywords, or by specifying them in a compact form with the
> `#+OPTIONS' keyword; or for a tree by setting properties (*note
>
> Properties and Columns::). Options set at a specific level
> override options set at a more general level.
>
> However instead I get:
>
> Table of Contents
> _________________
>
> 1 h1 no options
> 2 h1 toc:1
> 3 h1 toc:2
>
> What am I missing, and is there another way to vary the toc level per
> subtree?
>
> Thanks!
> Adam
>
signature.asc
Description: Message signed with OpenPGP using GPGMail