From: Kaushal Modi <kaushal.modi@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Carsten Dominik <dominik@uva.nl>, emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Add ability to force-enable TOC
Date: Wed, 20 Sep 2017 10:40:42 +0000 [thread overview]
Message-ID: <CAFyQvY2mjSe9kxVpit1ff6gqghgdR3nGhd10NLnaaktveZMd7w@mail.gmail.com> (raw)
In-Reply-To: <8760cdacpl.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1509 bytes --]
On Wed, Sep 20, 2017, 6:25 AM Nicolas Goaziou <mail@nicolasgoaziou.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.
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
[-- Attachment #2: Type: text/html, Size: 2889 bytes --]
next prev parent reply other threads:[~2017-09-20 13:40 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFyQvY2mjSe9kxVpit1ff6gqghgdR3nGhd10NLnaaktveZMd7w@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=dominik@uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.