From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Re: Add ability to force-enable TOC Date: Wed, 20 Sep 2017 10:40:42 +0000 Message-ID: References: <87shfia3qm.fsf@nicolasgoaziou.fr> <87h8vya2c3.fsf@nicolasgoaziou.fr> <8760cdacpl.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="f403045eaeaa6073ba05599c9c10" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44108) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dufEY-0005HB-VV for emacs-orgmode@gnu.org; Wed, 20 Sep 2017 09:40:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dufEW-0003ix-PR for emacs-orgmode@gnu.org; Wed, 20 Sep 2017 09:40:09 -0400 Received: from mail-yw0-x233.google.com ([2607:f8b0:4002:c05::233]:45515) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dufEW-0003iW-J8 for emacs-orgmode@gnu.org; Wed, 20 Sep 2017 09:40:08 -0400 Received: by mail-yw0-x233.google.com with SMTP id q80so1906745ywg.2 for ; Wed, 20 Sep 2017 06:40:08 -0700 (PDT) In-Reply-To: <8760cdacpl.fsf@nicolasgoaziou.fr> 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" To: Nicolas Goaziou Cc: Carsten Dominik , emacs-org list --f403045eaeaa6073ba05599c9c10 Content-Type: text/plain; charset="UTF-8" On Wed, Sep 20, 2017, 6:25 AM Nicolas Goaziou wrote: > 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. > Understood. IOW, do mixed numbered/unnumbered headings make sense in TOC? > Correct. That does not make sense to me. That is not my use case. >> 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? > I see your point. 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. > That might work.. treat num:nil differently than num:0 So here's the summary as per my understanding. Currently we support these: 1. Don't allow a mix of numbered and unnumbered headings in TOC. If any heading is unnumbered using the UNNUMBERED property, remove it from the TOC. 2. If we globally unnumber headings beyond a certain level by doing something like num:3, don't show headings beyond that level in the TOC. So num:0 wouldn't number any heading and also not generate the TOC. Now the 3rd use case (mine): 3. Unnumber all headings, but still keep them in TOC. So allow this 3rd use case when, may be, we have num:nil and not num:0? WDYT? @Carsten: Does this satisfy your use case too? > -- Kaushal Modi --f403045eaeaa6073ba05599c9c10 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Sep 20, 2017, 6:25 AM N= icolas Goaziou <mail@nicolasgo= aziou.fr> wrote:
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.

Understood.=C2=A0

IOW, do mixed numbered/unnumbered headings make sense in TOC?

Correct. That does not make sense to me. That = is not my use case.=C2=A0

>> 1. it makes all export back-ends cons= istent with TOC;
>>
>
>=C2=A0 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?

I see your point.=C2=A0

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

That might work.. treat num:nil differe= ntly than num:0

So here's the summary as per m= y understanding.
=C2=A0
Currently we support these:

1. Don't allow a mix of numbered and unnumbered h= eadings in TOC. If any heading is unnumbered using the UNNUMBERED property,= remove it from the TOC.=C2=A0

2. If we globally u= nnumber headings beyond a certain level by doing something like num:3, don&= #39;t show headings beyond that level in the TOC. So num:0 wouldn't num= ber any heading and also not generate the TOC.=C2=A0

Now the 3rd use case (mine):

3. Unnumber all he= adings, but still keep them in TOC.=C2=A0

So allow= this 3rd use case when, may be, we have num:nil and not num:0?
<= br>
WDYT?=C2=A0

@Carsten: Does this sati= sfy your use case too?
--

Kaushal Modi

--f403045eaeaa6073ba05599c9c10--