[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Add ability to force-enable TOC

From: Nicolas Goaziou
Subject: Re: [O] Add ability to force-enable TOC
Date: Wed, 20 Sep 2017 12:25:42 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)


Kaushal Modi <address@hidden> writes:

> On Tue, Sep 19, 2017 at 3:57 PM Nicolas Goaziou <address@hidden>
> wrote:
>> What is exactly the feature you are missing? Your example is a special
>> case where _no_ heading is numbered.
> I would not consider this as a special case. It is very common for HTML
> exports to not always number the headings.

I didn't say it was an unusual case. I said it didn't cover all the
use-cases. Maybe you are really needing a subset of the initial feature.
IOW, do mixed numbered/unnumbered headings make sense in TOC?

>> 1. it makes all export back-ends consistent with TOC;
>  I understand that. But would like a way to get back the earlier behavior
> too.

Then there is the other way around: how do we tell LaTeX to include both
numbered and unnumbered headings?

And: how do we distinguish @unnumberedsec from @heading in Texinfo?

> That way if the file has:
> #+OPTIONS: num:nil
> No TOC will be exported (even though the org-export-with-toc default is t).
> But if the file has:
> #+OPTIONS: num:nil toc:4
> As the toc value is a number, the TOC will be exported even though num is
> nil.

AFAICT, this doesn't solve any of the two concerns. What we can do for
"num:nil toc:4" can be done for "num:nil" alone.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]