From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [BUG] New exporter exports TOC twice Date: Sun, 28 Apr 2013 09:28:20 +0200 Message-ID: <871u9vktbf.fsf@gmail.com> 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: Received: from eggs.gnu.org ([208.118.235.92]:37081) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UWM24-0007ll-VL for emacs-orgmode@gnu.org; Sun, 28 Apr 2013 03:28:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UWM24-00047k-2V for emacs-orgmode@gnu.org; Sun, 28 Apr 2013 03:28:24 -0400 Received: from mail-wg0-x22a.google.com ([2a00:1450:400c:c00::22a]:55913) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UWM23-00047g-SM for emacs-orgmode@gnu.org; Sun, 28 Apr 2013 03:28:23 -0400 Received: by mail-wg0-f42.google.com with SMTP id m15so1220500wgh.5 for ; Sun, 28 Apr 2013 00:28:22 -0700 (PDT) In-Reply-To: (Carsten Dominik's message of "Sat, 27 Apr 2013 13:14:56 +0200") 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@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: Sebastien Vauban , emacs-orgmode@gnu.org Hello, Carsten Dominik writes: > 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). The problem is that #+TOC cannot be a strict equivalent to `org-export-with-toc', since the former cannot be introduced in the document template. Also, this change would require each user back-end developer to check for the presence of a TOC keyword with "headlines" value in the parse tree when handling :with-toc property. This is not complicated, but there are already many uncomplicated issues to think about when writing a back-end. In a nutshell, I don't think we should try to outsmart the user by ignoring his setup here. I suggest to improve the manual, if needed, instead. Regards, -- Nicolas Goaziou