From: John Muccigrosso <jmuccigr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: YAML closing delimiter
Date: Tue, 13 Oct 2015 09:11:35 -0700 (PDT) [thread overview]
Message-ID: <ebb2d862-397d-4e25-9e7e-fb54323a81c2@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1627 bytes --]
Pandoc uses
...
as its closing delimiter in the YAML block. It will also *read *
---
as one.
I see from the discussion when adding metadata to pandoc was being
discussed that gitit also uses the periods
<https://github.com/jgm/gitit/blob/22b7f66c79068a7da3a44d3ada8e5133ea334d95/README.markdown>
to close the front matter by the logic that sections constitutes a YAML
document which takes that delimiter.
<http://www.yaml.org/spec/1.2/spec.html#marker/document%20end/>
However this seems not to be the case in at least some other environments
that use YAML for front matter, like Jekyll
<http://jekyllrb.com/docs/frontmatter/> and Assemble
<http://assemble.io/docs/YAML-front-matter.html>.
For me, this means that the YAML front matter in pandoc-generated markdown
docs doesn't get read correctly in, for example, MacDown
<https://macdown.uranusjr.com>, which I use as a markdown editor, since it
uses Jekyll to handle the front matter.
I raise this because I wonder how common a problem this is, and what the
best solution might be.
--
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/ebb2d862-397d-4e25-9e7e-fb54323a81c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2736 bytes --]
next reply other threads:[~2015-10-13 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 16:11 John Muccigrosso [this message]
[not found] ` <ebb2d862-397d-4e25-9e7e-fb54323a81c2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-10-13 18:09 ` John MACFARLANE
[not found] ` <20151013180944.GB6891-4kKid1p5UN4xFjuZnxJpBp3lxR28IOakuDuwTybUTCk@public.gmane.org>
2015-10-13 20:54 ` John Muccigrosso
[not found] ` <08e65baa-f8d6-4437-af61-d106b36d1382-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-10-18 8:58 ` BPJ
[not found] ` <CADAJKhCt9EqV_v3XTrXq=oPFiOHnEsk5xEtB8wYiMKb3V0xDTw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-19 5:12 ` John MacFarlane
[not found] ` <20151019051220.GA15885-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2015-10-19 8:50 ` BP Jonsson
[not found] ` <5624AEDA.9050903-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-10-21 4:04 ` John MacFarlane
2015-10-18 18:39 ` John Muccigrosso
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=ebb2d862-397d-4e25-9e7e-fb54323a81c2@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).