From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: MANUAL.txt: `gfm` and `markdown_github` (GitHub-Flavored Markdown)
Date: Fri, 27 Oct 2017 16:24:40 -0700 [thread overview]
Message-ID: <20171027232440.GB82754@protagoras> (raw)
In-Reply-To: <01068d42-c013-4d0d-8439-92202707d485-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Thanks, I made some improvements here in d039f231cb.
+++ Kolen Cheung [Oct 27 17 01:16 ]:
> Currently, in the [1]MANUAL.txt line 3816, it mentions that both gfm
> and markdown_github are equivalent to a bunch of pandoc markdown
> extensions. But as far as I understand, gfm is a very different beast,
> and should not be understood as a bunch of pandoc markdown extensions
> activated, right?
>
> I didn’t make a pull request on this however, because I think more
> expanded description on the gfm variant is needed. For example, I guess
> it is impossible to add extension to gfm, unlike other variants (where
> the MANUAL.txt has mentioned this briefly at line 284). And for example
> I would have a question on how extra gfm extension that pandoc doesn’t
> have will be handled, e.g. the gfm checkbox.
>
>
> --
> 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 [2]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [3]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [4]https://groups.google.com/d/msgid/pandoc-discuss/01068d42-c013-4d0d-
> 8439-92202707d485%40googlegroups.com.
> For more options, visit [5]https://groups.google.com/d/optout.
>
>References
>
> 1. https://github.com/jgm/pandoc/blob/3f0ceaf6eef73500935b044e00aff0747569810e/MANUAL.txt#L3816
> 2. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 3. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 4. https://groups.google.com/d/msgid/pandoc-discuss/01068d42-c013-4d0d-8439-92202707d485-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 5. https://groups.google.com/d/optout
--
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/20171027232440.GB82754%40protagoras.
For more options, visit https://groups.google.com/d/optout.
prev parent reply other threads:[~2017-10-27 23:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 8:16 Kolen Cheung
[not found] ` <01068d42-c013-4d0d-8439-92202707d485-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-27 18:13 ` John MACFARLANE
2017-10-27 23:24 ` John MACFARLANE [this message]
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=20171027232440.GB82754@protagoras \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).