From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
Subject: Re: [BUG] New exporter exports TOC twice
Date: Sat, 27 Apr 2013 16:15:57 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Carsten Dominik wrote:
> On 27.4.2013, at 10:52, Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org> wrote:
>> Carsten Dominik wrote:
>>> On 24.4.2013, at 13:50, Nicolas Goaziou <n.goaziou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>>> Thorsten Jolitz <tjolitz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>>>> Exporting a Worg file with this header (#+TOC: headlines 2)
>>>>> exports the TOC twice in HTML export and ASCII export.
>>>> If you don't specify a toc item in the OPTIONS line, Org will use the
>>>> value of `org-export-with-toc', which is non-nil by default.
>>>> So, your example is equivalent to:
>>>> #+OPTIONS: toc:t
>>>> #+TOC: headline 2
>>>> Hence you get two tables of contents.
>>> Hmm, I understand the reasoning here - but my feeling says that
>>> the presence of one or more #+TOC lines in a file should probably
>>> overrule both #+OPTIONS: toc: and the content of org-export-with-toc.
>>> So in that case, your would then only get one TOC, at the
>>> location of that line.
>>> What do you think? Are there good reasons for not doing it
>>> as I propose?
>> Maybe what I'll say is stupid, but, in LaTeX, there's the minitoc package for
>> having a big TOC at the beginning of the document (default) + TOC per chapter,
>> which can be limited to less (or more) sublevels.
>> Maybe allowing to insert extra TOC here and there would allow one to make
>> something like that available to other backends? Though, as of today, I don't
>> think the TOC is limitable per org-level-1 headline...
> I am not saying multiple tocs should not be allowed. I am all for that.
> However, I think that by inserting a #+TOC line, the user indicates
> desire for local control. Therefore, org-export-with-toc should be ignored,
> and, by extension, also #+OPTIONS: toc (because this is really a local way
> to set org-export-with-toc).
OK, that's another point of view. I clearly have no objection for that
next prev parent reply other threads:[~2013-04-27 14:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 11:13 [BUG] New exporter exports TOC twice Thorsten Jolitz
2013-04-24 11:50 ` Nicolas Goaziou
2013-04-24 11:56 ` Thorsten Jolitz
2013-04-24 12:11 ` Nicolas Goaziou
2013-04-27 8:44 ` Carsten Dominik
2013-04-27 8:52 ` Sebastien Vauban
2013-04-27 11:14 ` Carsten Dominik
2013-04-27 14:15 ` Sebastien Vauban [this message]
2013-04-28 7:28 ` Nicolas Goaziou
2013-05-01 20:45 ` Carsten Dominik
2013-05-01 22:08 ` Nicolas Goaziou
2013-05-02 3:22 ` Carsten Dominik
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).