From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: [BUG] New exporter exports TOC twice Date: Wed, 1 May 2013 22:45:43 +0200 Message-ID: <5CD564EE-729C-4C08-A1AC-572025EEFC7A@gmail.com> References: <87k3ns89lk.fsf@gmail.com> <87bo949mgg.fsf@gmail.com> <717E4F0F-A573-4529-8BAD-0911E7BDDAC9@gmail.com> <86mwskxsmk.fsf@somewhere.org> <871u9vktbf.fsf@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:56268) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UXdu8-0004Ux-0B for emacs-orgmode@gnu.org; Wed, 01 May 2013 16:45:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UXdu7-00066h-56 for emacs-orgmode@gnu.org; Wed, 01 May 2013 16:45:31 -0400 Received: from mail-wi0-x229.google.com ([2a00:1450:400c:c05::229]:55734) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UXdu6-00066Q-UY for emacs-orgmode@gnu.org; Wed, 01 May 2013 16:45:31 -0400 Received: by mail-wi0-f169.google.com with SMTP id h11so5601138wiv.4 for ; Wed, 01 May 2013 13:45:29 -0700 (PDT) In-Reply-To: <871u9vktbf.fsf@gmail.com> 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: Nicolas Goaziou Cc: Sebastien Vauban , emacs-orgmode@gnu.org Hi Nicolas, On 28.4.2013, at 09:28, Nicolas Goaziou wrote: > Hello, >=20 > Carsten Dominik writes: >=20 >> 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). >=20 > 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. I am not sure I understand. What do you mean? > 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. An alternative would be that the parser already makes this change. Upon finding #+TOC, it would change the OPTION value in the parse tree. >=20 > 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. That is certainly an alternative, once I have understood the issues. Thanks for your patience. - Carsten=