From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: YAML closing delimiter
Date: Tue, 13 Oct 2015 11:09:44 -0700 [thread overview]
Message-ID: <20151013180944.GB6891@D25Q40BGFY13.Berkeley.EDU> (raw)
In-Reply-To: <ebb2d862-397d-4e25-9e7e-fb54323a81c2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Best solution would be to ask these other processors to
support ... as closing delimiter -- since after all this
is a standard YAML. (Another advantage is that if you
use ---, many markdown syntax highlighters will highlight the
last line of your metadata as a title, which looks bad.)
+++ John Muccigrosso [Oct 13 15 09:11 ]:
> 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 [1]gitit also uses the periods to close the front matter
> by the logic that sections constitutes a YAML document which [2]takes
> that delimiter.
> However this seems not to be the case in at least some other
> environments that use YAML for front matter, like [3]Jekyll and
> [4]Assemble.
> For me, this means that the YAML front matter in pandoc-generated
> markdown docs doesn't get read correctly in, for example, [5]MacDown,
> 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 [6]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [7]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [8]https://groups.google.com/d/msgid/pandoc-discuss/ebb2d862-397d-4e25-
> 9e7e-fb54323a81c2%40googlegroups.com.
> For more options, visit [9]https://groups.google.com/d/optout.
>
>References
>
> 1. https://github.com/jgm/gitit/blob/22b7f66c79068a7da3a44d3ada8e5133ea334d95/README.markdown
> 2. http://www.yaml.org/spec/1.2/spec.html#marker/document end/
> 3. http://jekyllrb.com/docs/frontmatter/
> 4. http://assemble.io/docs/YAML-front-matter.html
> 5. https://macdown.uranusjr.com/
> 6. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 7. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 8. https://groups.google.com/d/msgid/pandoc-discuss/ebb2d862-397d-4e25-9e7e-fb54323a81c2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 9. https://groups.google.com/d/optout
next prev parent reply other threads:[~2015-10-13 18:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 16:11 John Muccigrosso
[not found] ` <ebb2d862-397d-4e25-9e7e-fb54323a81c2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-10-13 18:09 ` John MACFARLANE [this message]
[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=20151013180944.GB6891@D25Q40BGFY13.Berkeley.EDU \
--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).