From: Adam Spiers <orgmode@adamspiers.org>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>,
Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: different toc levels per headline?
Date: Thu, 26 Sep 2013 16:50:04 +0100 [thread overview]
Message-ID: <20130926155004.GF15620@pacific.linksys.moosehall> (raw)
In-Reply-To: <874n973bk6.fsf@gmail.com>
On Thu, Sep 26, 2013 at 04:24:57PM +0200, Nicolas Goaziou wrote:
> Carsten Dominik <carsten.dominik@gmail.com> writes:
> > On 26.9.2013, at 14:16, Adam Spiers <orgmode@adamspiers.org> 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.
Cheers,
Adam
prev parent reply other threads:[~2013-09-26 15:50 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
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 [this message]
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=20130926155004.GF15620@pacific.linksys.moosehall \
--to=orgmode@adamspiers.org \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.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 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.