From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Sebastien Vauban <sva-news@mygooglest.com>, emacs-orgmode@gnu.org
Subject: Re: [BUG] New exporter exports TOC twice
Date: Sun, 28 Apr 2013 09:28:20 +0200 [thread overview]
Message-ID: <871u9vktbf.fsf@gmail.com> (raw)
In-Reply-To: <C47755DD-44C0-4948-8B44-35808BBBD09F@gmail.com> (Carsten Dominik's message of "Sat, 27 Apr 2013 13:14:56 +0200")
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.
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
next prev parent reply other threads:[~2013-04-28 7:28 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 [this message]
2013-05-01 20:45 ` Carsten Dominik
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=871u9vktbf.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sva-news@mygooglest.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).