I created https://github.com/jgm/pandoc/issues/8140 with some suggestions for documentation improvements. On Wed, 22 Jun 2022 at 09:24, William Lupton wrote: > I'm confused. You seem to have taken a step back (the latest error is > saying that the input file doesn't exist). You started with this: > > *$ pandoc GENIe_scripting_reference.md -o GENIe_scripting_reference.pdf* > *YAML parse exception at line 9, column 9: mapping values are not allowed > in this context* > > Starting with the downloaded file, this worked for me: > > > *$ perl -pe 's/^---$/---\n/igs' GENIe_scripting_reference.md > >GENIe_scripting_reference.fixed.md > $ pandoc > GENIe_scripting_reference.fixed.md > -o > GENIe_scripting_reference.pdf* > > Note that Albert's suggestion (i.e., ensure that "---" lines are always > followed by a blank line) is much better than mine. My suggestion caused > problems with unintentional tables (due, I suppose, to "- - -" lines not > being followed by blank lines). > > William > > On Wed, 22 Jun 2022 at 00:43, almaghfuur lahu > wrote: > >> I forgot i'd better believe i put wrong command. Here'd be the valid one: >> >> >> *$ pandoc -f markdown -t pdf GENIe_scripting_reference.md -o >> GENIe_scripting_reference.pdfpandoc: GENIe_scripting_reference.md: >> openBinaryFile: does not exist (No such file or directory)* >> >> as i'm noob in mark up/down file processing, still have no idea how to >> solve it >> On Tuesday, 21 June 2022 at 22:03:02 UTC+7 William Lupton wrote: >> >>> 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 >>> wrote: >>> >>>> >>>> William Lupton 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-discus...-/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/0c95c0e6-1558-468b-b224-278d99c31332n%40googlegroups.com >> >> . >> > -- 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_xxjFnjwXaRVdm41TOxQqg8C8xpFR%2B376pWaUFCuo5wBwLg%40mail.gmail.com.