From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: John Lapeyre
<john.lapeyre-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Converting from yaml no longer possible
Date: Fri, 17 Apr 2020 10:52:13 -0700 [thread overview]
Message-ID: <m23692c84y.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <7a408d67-fe8d-4809-a5b0-a75824347b2f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
John Lapeyre <john.lapeyre-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> So instead, I tried using "-f markdown" on the command line. In this case,
> pandoc 2.9.2.1 gives this warning:
> [WARNING] Could not parse YAML metadata at line 953 column 1: Duplicate key
> in mapping: Scalar (Pos {posByteOffset = 16004, posCharOffset = 15999,
> posLine = 386, posColumn = 0}) (SUnknown Nothing "educationtitle")
Try looking at line 386 or thereabouts. Do you have two keys
marked educationtitle? That would be invalid YAML. It could be
that the new YAML parser we're using is stricter.
next prev parent reply other threads:[~2020-04-17 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 3:04 John Lapeyre
[not found] ` <0540a74b-0bc7-46ce-bc0c-4fb0579a1e5a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-04-17 3:21 ` Brandon Keith Biggs
[not found] ` <CAKAWQkUyr+j5-9ioeVeSd=yR0g2Kwz4oOpMmhX4cMKCz_7jq5Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-04-17 3:22 ` Brandon Keith Biggs
2020-04-17 16:30 ` John MacFarlane
[not found] ` <m2tv1icbwe.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-04-17 17:35 ` John Lapeyre
[not found] ` <7a408d67-fe8d-4809-a5b0-a75824347b2f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-04-17 17:50 ` John MacFarlane
2020-04-17 17:52 ` John MacFarlane [this message]
2020-04-17 18:18 ` John Lapeyre
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=m23692c84y.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=john.lapeyre-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).