emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Sebastien Vauban <sva-news@mygooglest.com>, emacs-orgmode@gnu.org
Subject: Re: [BUG] New exporter exports TOC twice
Date: Wed, 1 May 2013 22:45:43 +0200	[thread overview]
Message-ID: <5CD564EE-729C-4C08-A1AC-572025EEFC7A@gmail.com> (raw)
In-Reply-To: <871u9vktbf.fsf@gmail.com>

Hi Nicolas,

On 28.4.2013, at 09:28, Nicolas Goaziou <n.goaziou@gmail.com> wrote:

> Hello,
> Carsten Dominik <carsten.dominik@gmail.com> 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.

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.

> 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

  reply	other threads:[~2013-05-01 20:45 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
2013-04-28  7:28         ` Nicolas Goaziou
2013-05-01 20:45           ` Carsten Dominik [this message]
2013-05-01 22:08             ` Nicolas Goaziou
2013-05-02  3:22               ` Carsten Dominik

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:

  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=5CD564EE-729C-4C08-A1AC-572025EEFC7A@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    --cc=sva-news@mygooglest.com \


* 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).