public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: William Lupton <wlupton-QSt+ys/nuMyEUIsrzH9SikB+6BGkLq7r@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Got this error on Linux' one
Date: Tue, 21 Jun 2022 16:02:46 +0100	[thread overview]
Message-ID: <CAEe_xximH93ZyPmbVwPUVonnwTBgj1WB-2x2GMF_+bBefAW=EA@mail.gmail.com> (raw)
In-Reply-To: <87a6a6nmug.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1720 bytes --]

Thanks. Is that documented? From a quick scan I didn't see it at
https://pandoc.org/MANUAL.html#extension-yaml_metadata_block (but maybe I
missed it).

On Tue, 21 Jun 2022 at 14:54, Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
wrote:

>
> William Lupton <wlupton-QSt+ys/nuMyEUIsrzH9SikB+6BGkLq7r@public.gmane.org> writes:
>
> > Perhaps there are some heuristics that control whether pandoc decides
> > that a given block is YAML. Maybe lines like this one are being taken
> > to be YAML?
>
> The heuristic applied by pandoc is "if there's a line containing the
> string `---`, and if that line is not followed by a blank line, and if
> there's a closing `---` later in the text, then treat it as a YAML
> block.
>
> So adding a blank line after `---` should fix this as well.
>
>
> --
> Albert Krewinkel
> GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124
>
> --
> 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/87a6a6nmug.fsf%40zeitkraut.de
> .
>

-- 
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/CAEe_xximH93ZyPmbVwPUVonnwTBgj1WB-2x2GMF_%2BbBefAW%3DEA%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 2812 bytes --]

  parent reply	other threads:[~2022-06-21 15:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21  9:27 almaghfuur lahu
     [not found] ` <6a390800-289b-4932-9d26-b6158f76aa11n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-21  9:37   ` William Lupton
     [not found]     ` <CAEe_xxje9j4rC3a9MtNSgeDocvStDsycapBS0y8GBo0Mo3qfDg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-06-21  9:55       ` almaghfuur lahu
     [not found]         ` <4ce1cfe9-8c01-4882-af2d-38ffacb7df3cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-21 10:37           ` William Lupton
     [not found]             ` <CAEe_xxjEx9ttLuEmyb=0N7nJ8=o5T689krJVTgPFJQRPVTvnkw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-06-21 13:21               ` Albert Krewinkel
     [not found]                 ` <87a6a6nmug.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-06-21 15:02                   ` William Lupton [this message]
     [not found]                     ` <CAEe_xximH93ZyPmbVwPUVonnwTBgj1WB-2x2GMF_+bBefAW=EA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-06-21 23:43                       ` almaghfuur lahu
     [not found]                         ` <0c95c0e6-1558-468b-b224-278d99c31332n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-22  8:24                           ` William Lupton
     [not found]                             ` <CAEe_xxgjXZhV3XqOpstoPrsbsEiCidqG72Prx9SnL=C1tRAq7Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-06-22  8:50                               ` William Lupton
     [not found]                                 ` <CAEe_xxjFnjwXaRVdm41TOxQqg8C8xpFR+376pWaUFCuo5wBwLg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-06-22 10:54                                   ` almaghfuur lahu

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='CAEe_xximH93ZyPmbVwPUVonnwTBgj1WB-2x2GMF_+bBefAW=EA@mail.gmail.com' \
    --to=wlupton-qst+ys/numyeuisrzh9sikb+6bgklq7r@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).