public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Zev Spitz <spitzzev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: "expected newline" when converting Markdown to HTML
Date: Wed, 5 Feb 2020 04:56:05 -0800 (PST)	[thread overview]
Message-ID: <fc449ba3-6a6d-4d89-b43e-8954fcacbb95@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1023 bytes --]

I have the following markdown:

<div dir="rtl" markdown="1">
    
# Header
    
First paragraph
    
</div>

which I am trying to convert to a PDF within a GitHub Action 
<https://github.com/zspitz/tidepool-hebrew-docs/runs/426905893?check_suite_focus=true>.However, 
this fails with:

docs/test.md: line 2: syntax error: unexpected newline


If I had to guess, I would say the parser is expecting HTML, and the second 
line of the text should be additional HTML or other non-whitespace content, 
instead of a blank line.

How can I fix this?

(NB Would it be helpful to include the output of --list-extensions?)

-- 
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/fc449ba3-6a6d-4d89-b43e-8954fcacbb95%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2720 bytes --]

             reply	other threads:[~2020-02-05 12:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-05 12:56 Zev Spitz [this message]
     [not found] ` <fc449ba3-6a6d-4d89-b43e-8954fcacbb95-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-02-05 17:25   ` John MacFarlane
     [not found]     ` <yh480kimklx7yl.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-02-05 20:50       ` Zev Spitz

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=fc449ba3-6a6d-4d89-b43e-8954fcacbb95@googlegroups.com \
    --to=spitzzev-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).