From: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: --defaults issue: "Multiple YAML documents encountered"
Date: Wed, 6 Sep 2023 08:22:08 +0200 [thread overview]
Message-ID: <CADAJKhCnJ9fDf+HdxysDDW=mvPjQtCCOtYnujYypo8AJXmTPaw@mail.gmail.com> (raw)
In-Reply-To: <ZPedbTNoS6KKoG2l@localhost>
[-- Attachment #1: Type: text/plain, Size: 1733 bytes --]
Den tis 5 sep. 2023 23:29Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org> skrev:
> > The yaml used to reproduce the error is absolutely
> > minimal (just two lines with three dashes each will reproduce the
> error).
>
> It doesn't happen to me when I end the file with three points instead of
> three dashes.
>
Three dots is the correct way to end a YAML stream, variations permitted by
Pandoc metadata blocks and other tools notwithstanding. Three dashes signal
the *start* of a YAML document within a stream, so if you "end" the file
with three dashes some parsers will (correctly) see that as the start of a
second, empty document, and may discard all but the last document in the
stream and ergo you get an empty or invalid value. I believe that correctly
they ought to discard all but the *first* document (I have no time to look
it up in the spec), but there you have it.
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/ZPedbTNoS6KKoG2l%40localhost
> .
>
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhCnJ9fDf%2BHdxysDDW%3DmvPjQtCCOtYnujYypo8AJXmTPaw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2938 bytes --]
prev parent reply other threads:[~2023-09-06 6:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 21:22 t t
[not found] ` <f4fee45c-4f45-4b96-a12e-ce203ca06dfen-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-09-05 21:28 ` Bastien DUMONT
2023-09-05 23:51 ` t t
[not found] ` <da60dc79-7264-4141-869f-c3acbdc958adn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-09-06 7:08 ` Bastien DUMONT
2023-09-06 14:42 ` t t
2023-09-06 6:22 ` BPJ [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='CADAJKhCnJ9fDf+HdxysDDW=mvPjQtCCOtYnujYypo8AJXmTPaw@mail.gmail.com' \
--to=melroch-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).