From: Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: --defaults issue: "Multiple YAML documents encountered"
Date: Wed, 6 Sep 2023 07:08:51 +0000 [thread overview]
Message-ID: <ZPglgythiDmnRK4Q@localhost> (raw)
In-Reply-To: <da60dc79-7264-4141-869f-c3acbdc958adn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
If you still test an empty YAML file, the parser is right: is expects a mapping after the line of dashes, and you don't provide one. Please fill you YAML file!
Le Tuesday 05 September 2023 à 04:51:41PM, t t a écrit :
> Hm, I just tried that - that gives me an aeson exception:
> Aeson exception:
>
> Error in $: Expected a mapping
>
>
>
> shell returned 64
>
> On Tuesday, September 5, 2023 at 5:28:21 PM UTC-4 Bastien DUMONT wrote:
>
> > 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.
>
> --
> 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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit [2]https://groups.google.com/d/msgid/
> pandoc-discuss/da60dc79-7264-4141-869f-c3acbdc958adn%40googlegroups.com.
>
> References:
>
> [1] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [2] https://groups.google.com/d/msgid/pandoc-discuss/da60dc79-7264-4141-869f-c3acbdc958adn%40googlegroups.com?utm_medium=email&utm_source=footer
--
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/ZPglgythiDmnRK4Q%40localhost.
next prev parent reply other threads:[~2023-09-06 7:08 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 [this message]
2023-09-06 14:42 ` t t
2023-09-06 6:22 ` BPJ
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=ZPglgythiDmnRK4Q@localhost \
--to=bastien.dumont-vwifzpto/vqstnjn9+bgxg@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).