From: t t <tobias.tschiedl-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 07:42:31 -0700 (PDT) [thread overview]
Message-ID: <411c4534-ad29-4e8b-991d-b83eef0b66can@googlegroups.com> (raw)
In-Reply-To: <ZPglgythiDmnRK4Q@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 2664 bytes --]
Thanks for the explanations, now I got it! Indeed I hadn't known yaml
outside of pandoc headers, so the three dots were news to me... I think I
did try them at some point yesterday but there was some other ill-formed
stuff in the file that kept giving me aeson errors (which seem to be
notoriously inscrutable?)... so now I rewrote that file from scratch and it
works.
Thanks!
On Wednesday, September 6, 2023 at 3:09:00 AM UTC-4 Bastien DUMONT wrote:
> 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-discus...-/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-discus...-/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/411c4534-ad29-4e8b-991d-b83eef0b66can%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 4509 bytes --]
next prev parent reply other threads:[~2023-09-06 14:42 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 [this message]
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=411c4534-ad29-4e8b-991d-b83eef0b66can@googlegroups.com \
--to=tobias.tschiedl-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).