public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: christophe dervieux <christophe.dervieux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: table of content with headers inside divs
Date: Wed, 2 Feb 2022 05:47:07 -0800 (PST)	[thread overview]
Message-ID: <a8b4c757-0182-473d-ae9b-e0ab2271b234n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1342 bytes --]



Hello, 

I am trying to understand if this is a bug or not. 

I found several old issues on Github where it seems it was not possible at 
the time to have some headers inside Fenced Divs to be in the TOC. However, 
I seems to have been fixed. 

This is working for example 

# External 

::: custom
## Internal

content
:::

End of document

When rendered to HTML with Pandoc, H2 header “Internal” is inside the TOC. 

However, as long as there is other header of the same level inside the divs 
it won’t be in the TOC anymore

# External 

::: custom
## Internal

content
## Internal 2

content
:::

End of document

Is this not supported to have several headers like inside a divs ? Because 
of difficulty to know the hierarchy for sure ? 

Is the behavior behind the table-of-content document somewhere ? I can’t 
say if this is a bug or a feature. 

Thank you
​

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a8b4c757-0182-473d-ae9b-e0ab2271b234n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 5903 bytes --]

             reply	other threads:[~2022-02-02 13:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02 13:47 christophe dervieux [this message]
     [not found] ` <a8b4c757-0182-473d-ae9b-e0ab2271b234n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-02-02 18:25   ` John MacFarlane
     [not found]     ` <m2v8xxcei5.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2022-02-02 18:44       ` BPJ
2022-02-03  9:21       ` christophe dervieux
     [not found]         ` <f11c2921-244e-4833-a325-7a417c904853n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-02-03  9:29           ` Albert Krewinkel

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=a8b4c757-0182-473d-ae9b-e0ab2271b234n@googlegroups.com \
    --to=christophe.dervieux-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /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.
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 NNTP newsgroup(s).