public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "carlosj...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <carlosjosepita-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: TOC in gfm output
Date: Thu, 20 May 2021 22:09:58 -0700 (PDT)	[thread overview]
Message-ID: <9612aca4-1c8a-4797-88da-ec7ee792c56fn@googlegroups.com> (raw)


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

Hi all,

I would like to produce gfm from pandoc markdown. One of the features I'm 
interested in is TOC generation. Now, I can get a TOC by passing the --toc 
flag to pandoc, but what I want is to specify metadata in each document 
that enables/disables TOC creation. Unfortunately, if I add toc=true as 
metadata I'm stuck with these two alternatives:

1. When the output is markdown, the entire metadata block is preserved 
verbatim.

2. When the output is gfm, the entire metadata block is removed.

In neither of these cases a TOC is inserted into the document, as with the 
--flag.

What am I missing? Is this really possible? The ability to output a 
markdown TOC is there, what is not obvious to me is how to enable that from 
the document itself.

Thank you in advance,
Carlos

-- 
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/9612aca4-1c8a-4797-88da-ec7ee792c56fn%40googlegroups.com.

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

             reply	other threads:[~2021-05-21  5:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21  5:09 carlosj...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [this message]
     [not found] ` <9612aca4-1c8a-4797-88da-ec7ee792c56fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-21  5:15   ` carlosj...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org

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=9612aca4-1c8a-4797-88da-ec7ee792c56fn@googlegroups.com \
    --to=carlosjosepita-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).