emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Carsten Dominik <dominik@uva.nl>
Cc: emacs-org list <emacs-orgmode@gnu.org>,
	Kaushal Modi <kaushal.modi@gmail.com>
Subject: Re: Add ability to force-enable TOC
Date: Tue, 19 Sep 2017 21:27:13 +0200	[thread overview]
Message-ID: <87shfia3qm.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CADn3Z2JBrnSxs74PfYqVmENoREUzwuSZ8D7iQV8TBZmLB4G2RA@mail.gmail.com> (Carsten Dominik's message of "Tue, 19 Sep 2017 17:33:18 +0200")

Hello,

Carsten Dominik <dominik@uva.nl> writes:

> 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 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?

The change was intended. The idea was discussed on the ML. You may want
to check the thread.

This is on par with, e.g., what LaTeX does.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2017-09-19 19:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19 14:49 Add ability to force-enable TOC Kaushal Modi
2017-09-19 15:00 ` Kaushal Modi
2017-09-19 15:33 ` Carsten Dominik
2017-09-19 19:27   ` Nicolas Goaziou [this message]
2017-09-19 19:31     ` Kaushal Modi
2017-09-19 19:57       ` Nicolas Goaziou
2017-09-19 20:12         ` Kaushal Modi
2017-09-20 10:25           ` Nicolas Goaziou
2017-09-20 10:40             ` Kaushal Modi
2017-09-22 13:32               ` Matt Lundin
2017-09-20  8:53       ` Rasmus
2017-09-20 14:15         ` Rasmus
2017-09-20  8:14     ` Carsten Dominik
2017-09-20  8:54       ` Rasmus
2017-09-20 10:04       ` Kaushal Modi

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=87shfia3qm.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=dominik@uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaushal.modi@gmail.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).