From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Add ability to force-enable TOC Date: Tue, 19 Sep 2017 17:33:18 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="f403045c48bc57930805598c9579" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43744) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1duKWt-0002FG-1f for emacs-orgmode@gnu.org; Tue, 19 Sep 2017 11:33:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1duKWs-00017c-3R for emacs-orgmode@gnu.org; Tue, 19 Sep 2017 11:33:43 -0400 Received: from mail-wm0-x236.google.com ([2a00:1450:400c:c09::236]:43884) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1duKWr-00016c-SV for emacs-orgmode@gnu.org; Tue, 19 Sep 2017 11:33:42 -0400 Received: by mail-wm0-x236.google.com with SMTP id a137so430392wma.0 for ; Tue, 19 Sep 2017 08:33:40 -0700 (PDT) In-Reply-To: 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: Kaushal Modi Cc: emacs-org list --f403045c48bc57930805598c9579 Content-Type: text/plain; charset="UTF-8" On Tue, Sep 19, 2017 at 4:49 PM, Kaushal Modi wrote: > Hello, > > I have use-cases where I don't like to see the headings numbered but still > want the TOC to be generated. > > I have this in many of my Org files: > > #+OPTIONS: num:nil H:4 > > But after commit bd23781[1], that has stopped working i.e. no TOC is > created because of num:nil. > I would see this as a bug - clearly it makes sense to have a TOC without numbering. Nicolas, was this an oversight, or was this change intended? Carsten > > Can we enforce the TOC generation using the "toc:" option. Below does not > work at the moment, but would like that to work. > > #+OPTIONS: num:nil H:4 toc:4 > > Thanks. > > [1]: http://orgmode.org/cgit.cgi/org-mode.git/commit/?id= > bd2378161e76932103c9ef1f8343ffcc0d275007 > -- > > Kaushal Modi > --f403045c48bc57930805598c9579 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, Sep 19, 2017 at 4:49 PM, Kaushal Modi <kaushal.modi@gmail= .com> wrote:
Hello,

I have use-cases where I don't like to see= the headings numbered but still want the TOC to be generated.
I have this in many of my Org files:

= #+OPTIONS: num:nil H:4

But after commit bd2378= 1[1], that has stopped working i.e. no TOC is created because of num:nil.

I would see this as a bug - clea= rly it makes sense to have a TOC without numbering.

Nicolas, was this an oversight, or was this change intended?
Carsten
=C2=A0
<= div dir=3D"ltr">

Can we enforce the TOC generation using= the "toc:" option. Below does not work at the moment, but would = like that to work.

#+OPTIONS: num:nil H:4 toc:4 = =C2=A0

Thanks.

--

Kaushal Modi


--f403045c48bc57930805598c9579--