[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] different toc levels per headline?

From: Adam Spiers
Subject: Re: [O] different toc levels per headline?
Date: Thu, 26 Sep 2013 16:50:04 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

On Thu, Sep 26, 2013 at 04:24:57PM +0200, Nicolas Goaziou wrote:
> Carsten Dominik <address@hidden> writes:
> > On 26.9.2013, at 14:16, Adam Spiers <address@hidden> wrote:
> >> Thanks a lot for the reply.  However, what you say seems to directly
> >> contradict this sentence in the manual:
> >> 
> >>    Options set at a specific level override options set at a more
> >>    general level.
> >> 
> >> which is why this confused me.  I guess that sentence was intended to
> >> refer only to subtree exports, not whole document exports, but that
> >> meaning was not clear to me.
> >
> > I think it means this in general, but I also think that toc creation
> > is done at a global level, and not recursive in the tree.  Maybe Nicolas
> > has an authoritative answer on this one.
> Not really. For the record, the full paragraph is:
>   Export options can be set: globally with variables; for an individual
>   file by making variables buffer-local with 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.
>   Options set at a specific level override options set at a more general
>   level.

Right, I quoted that in my original post :-)

> There are three ways (four if you use a subtree export) to tweak export
> settings. The last sentence means that more specific ways have
> precedence over more general ones. IOW:
>   #+OPTIONS or #+KEYWORDS > variables
> and in the case of a subtree export:
>   Properties > #+OPTIONS or #+KEYWORDS > variables

Sure, I understood that.  But AFAICS it doesn't provide a way of
controlling the depth of headings within the ToC _per_heading_,
which as I suggested in my previous email shouldn't be a particularly
rare use case.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]