From: Adam Spiers <orgmode@adamspiers.org>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: different toc levels per headline?
Date: Thu, 26 Sep 2013 13:16:35 +0100 [thread overview]
Message-ID: <20130926121635.GE15620@pacific.linksys.moosehall> (raw)
In-Reply-To: <9D7DDF81-6925-481C-A1B6-8338167B0106@gmail.com>
Hi Carsten,
On Thu, Sep 26, 2013 at 01:15:56PM +0200, Carsten Dominik wrote:
> 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.
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. Perhaps it can be clarified via a small
tweak?
> Generating a single document should follow one set of rules, not
> many.
I agree that KISS is valuable when designing the rules. However, it
also seems a perfectly reasonable requirement to be able to control
the toc: level per subtree during a whole document export, since in an
arbitrary document there's no guarantee that every headline has the
same depth. E.g. one chapter may have a few deep subsections, whereas
another may contain lots of shallow subsections. In these scenarios
it is clearly beneficial to allow the author to choose which
subsections appear in the ToC.
So is there a way of achieving this? If not, please consider this a
feature request ;-)
Thanks!
Adam
next prev parent reply other threads:[~2013-09-26 12: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
2013-09-26 12:16 ` Adam Spiers [this message]
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
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=20130926121635.GE15620@pacific.linksys.moosehall \
--to=orgmode@adamspiers.org \
--cc=emacs-orgmode@gnu.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 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).