From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Line breaks (Was: Re: Unsupported extension in Commonmark_x resulting in alternative output)
Date: Fri, 24 Jun 2022 10:06:21 -0400 [thread overview]
Message-ID: <c42c982d-0fb1-a895-78e3-ac39bb737b57@usa.net> (raw)
In-Reply-To: <m25ykrqgmk.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
On 6/23/22 4:17 PM, John MacFarlane wrote:
> I'll change the writer so it uses \ + newline for
> commonmark + commonmark variants.
Thanks, that will be a lot more stable to work with I believe.
Daniel T. Staal
--
---------------------------------------------------------------
This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------
next prev parent reply other threads:[~2022-06-24 14:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 19:23 Unsupported extension in Commonmark_x resulting in alternative output Thomas Byskov Dalgaard
[not found] ` <7F040099-8F18-41C2-BB05-0A4658311704-AHfMSizzl90sTMJHDOTzqX9LOBIZ5rWg@public.gmane.org>
2022-06-23 6:21 ` John MacFarlane
[not found] ` <m2pmizrjc5.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-06-23 13:19 ` Line breaks (Was: Re: Unsupported extension in Commonmark_x resulting in alternative output) Daniel Staal
[not found] ` <377aa06e-714c-ba4a-5445-dc9d518b95ab-Jdbf3xiKgS8@public.gmane.org>
2022-06-23 19:11 ` BPJ
2022-06-23 20:17 ` John MacFarlane
[not found] ` <m25ykrqgmk.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-06-23 20:51 ` Thomas Byskov Dalgaard
2022-06-24 14:06 ` Daniel Staal [this message]
2022-06-23 14:13 ` Unsupported extension in Commonmark_x resulting in alternative output 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=c42c982d-0fb1-a895-78e3-ac39bb737b57@usa.net \
--to=dstaal-jdbf3xikgs8@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).