public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Kolen Cheung <christian.kolen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Automatically generated a blog (inline) table of contents from Markdown
Date: Sat, 20 Apr 2019 13:41:16 -0700 (PDT)	[thread overview]
Message-ID: <6e7c6cb0-76c8-4146-abc8-f6f921e05916@googlegroups.com> (raw)
In-Reply-To: <9183d4df-7db3-4867-88a3-9340b778932f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]

You could write a pandoc filter to get the links. If you use python then try looking at Panflute on GitHub for its user guide.

To generate the markdown in other markdowns, you can use pandoc -t ... option, both markdown you mentioned are supported. See pandoc Manual for details. It will try to represent feature not present in the target markdown by its closest representation (sometimes HTML, or in the case of footnote a “pseudo” footnote that looks like a footnote.) You should try to see if it works in your case though.

If it doesn’t work than in the filter you may add custom ID per header you need and then create links to those directly.

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/6e7c6cb0-76c8-4146-abc8-f6f921e05916%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

  parent reply	other threads:[~2019-04-20 20:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-19 23:57 Patrick Kenny
     [not found] ` <9183d4df-7db3-4867-88a3-9340b778932f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-04-20 20:41   ` Kolen Cheung [this message]
     [not found]     ` <6e7c6cb0-76c8-4146-abc8-f6f921e05916-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-04-23  1:23       ` Patrick Kenny

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=6e7c6cb0-76c8-4146-abc8-f6f921e05916@googlegroups.com \
    --to=christian.kolen-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).