From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Cc: "ch_...\@web.de" <ch_819-S0/GAf8tV78@public.gmane.org>
Subject: Re: general attributes and yaml metadata block
Date: Sat, 22 Aug 2020 11:07:19 -0700 [thread overview]
Message-ID: <m2v9ha7dwo.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <CADAJKhAofn83Rb6P1k7eqoYEwXrKsyH7e0mJ+AJFKVe8XDnehw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>> Eventually they will be, when I've added enough extensions
>> to the commonmark parser that it can replace the current
>> markdown parser.
>>
>
> Does that mean that you will drop some extensions? I hope not. Probably
> every extension is essential to someone's workflow.
The idea would be to support most of them. There may be a few
uncommonly used ones that we'd consider dropping (in particular,
extensions that are incompatible with the core commonmark spec).
In any case, we'd keep the legacy parser available as an option
for a while, to ease the transition.
next prev parent reply other threads:[~2020-08-22 18:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 12:07 Christian Müller
[not found] ` <a0460a16-04eb-4ff8-8159-4a22138967b7o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-21 20:51 ` John MacFarlane
[not found] ` <m2h7svafjy.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-22 8:34 ` ch_...-S0/GAf8tV78@public.gmane.org
[not found] ` <b88f4db2-e711-41b5-8223-87f90447753fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-22 10:41 ` mb21
2020-08-22 16:08 ` John MacFarlane
[not found] ` <m24kou8xzd.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-22 16:52 ` BPJ
[not found] ` <CADAJKhAofn83Rb6P1k7eqoYEwXrKsyH7e0mJ+AJFKVe8XDnehw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-08-22 18:07 ` John MacFarlane [this message]
[not found] ` <m2v9ha7dwo.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-24 9:59 ` BPJ
[not found] ` <CADAJKhA_NN8XUq8GXUJn4ObasyRQrw5inXgtatWvwRPOcSmzoQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-08-24 16:56 ` John MacFarlane
[not found] ` <m2o8n0x9s8.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-24 17:50 ` BPJ
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=m2v9ha7dwo.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=ch_819-S0/GAf8tV78@public.gmane.org \
--cc=melroch-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).