From: John Muccigrosso <jmuccigr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Horizontal rule immediately after text
Date: Tue, 26 Apr 2016 20:11:36 -0700 (PDT) [thread overview]
Message-ID: <afc96e82-2771-45f4-af80-ca5900ab6ade@googlegroups.com> (raw)
In-Reply-To: <5563EB9704768F3DF0386FE4-3uUC32ntyBiNj9Bq2fkWzw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1849 bytes --]
On Tuesday, April 26, 2016 at 6:17:20 PM UTC-4, Daniel Staal wrote:
>
> At the moment, probably the only reason would be compatibility with other
> versions of Pandoc - it's the type of thing where a 'random' change could
> break people's documents in odd ways.
>
> That said - Pandoc can also read Markdown as CommonMark, and the
> CommonMark
> spec doesn't require the blank line there. So if you don't mind losing
> some of Pandoc's extensions to the spec, you can get the more common
> behavior. (And it might be worth the thought - if CommonMark is supposed
> to be an evolution of the Markdown spec - of: Does Pandoc want to adhere
> to
> CommonMark in this case?)
1. Yes, I do mind losing the pandoc goodness.
2. I tend to agree about following CommonMark, but in this case that also
means following the original markdown, which remains a source of confusion
to me.
But, if pandoc were to become compatible with this approach, is the
backwards compatibility a big deal? How often is someone writing a line of
text with a following series of three asterisks or underscores, for
example? That is, these hr-makers would seem to be extremely unlikely to
occur in other contexts, so such a change would be unlikely to have a big
impact on anyone, no?
--
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/afc96e82-2771-45f4-af80-ca5900ab6ade%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2504 bytes --]
prev parent reply other threads:[~2016-04-27 3:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 17:37 John Muccigrosso
[not found] ` <7d2caf01-890c-4686-8ec3-4737092f0457-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-04-26 18:31 ` John MACFARLANE
[not found] ` <20160426183115.GA34351-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2016-04-26 19:24 ` John Muccigrosso
[not found] ` <77827528-e1da-4ca8-9878-67513c7ba0d5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-04-26 22:17 ` Daniel Staal
[not found] ` <5563EB9704768F3DF0386FE4-3uUC32ntyBiNj9Bq2fkWzw@public.gmane.org>
2016-04-27 3:11 ` John Muccigrosso [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=afc96e82-2771-45f4-af80-ca5900ab6ade@googlegroups.com \
--to=jmuccigr-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).