From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sebastien Vauban" Subject: Re: [BUG] New exporter exports TOC twice Date: Sat, 27 Apr 2013 16:15:57 +0200 Message-ID: <8638ucxdnm.fsf@somewhere.org> References: <87k3ns89lk.fsf@gmail.com> <87bo949mgg.fsf@gmail.com> <717E4F0F-A573-4529-8BAD-0911E7BDDAC9@gmail.com> <86mwskxsmk.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Hi Carsten, Carsten Dominik wrote: > On 27.4.2013, at 10:52, Sebastien Vauban wrote: >> Carsten Dominik wrote: >>> On 24.4.2013, at 13:50, Nicolas Goaziou wrote: >>>> Thorsten Jolitz 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 behavior. Best regards, Seb -- Sebastien Vauban