From: Carsten Dominik <carsten.dominik@gmail.com>
To: Adam Spiers <orgmode@adamspiers.org>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: different toc levels per headline?
Date: Thu, 26 Sep 2013 13:15:56 +0200 [thread overview]
Message-ID: <9D7DDF81-6925-481C-A1B6-8338167B0106@gmail.com> (raw)
In-Reply-To: <20130926110130.GD15620@pacific.linksys.moosehall>
[-- Attachment #1: Type: text/plain, Size: 1890 bytes --]
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 <orgmode@adamspiers.org> 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
>
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2013-09-26 11:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 11:01 different toc levels per headline? Adam Spiers
2013-09-26 11:15 ` Carsten Dominik [this message]
2013-09-26 12:16 ` Adam Spiers
2013-09-26 12:24 ` Carsten Dominik
2013-09-26 14:24 ` Nicolas Goaziou
2013-09-26 15:50 ` Adam Spiers
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9D7DDF81-6925-481C-A1B6-8338167B0106@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=orgmode@adamspiers.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.