From: "'Andrew Pashkin' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: How to make Pandoc parse headings not preceded by empty lines?
Date: Thu, 23 Nov 2023 18:32:26 +0100 [thread overview]
Message-ID: <ee3c5844-ba4f-41d4-a68b-acc237996a03@gmx.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
Let's take such a Markdown file
Text
text
some text
## Heading
Blah blah
Github will be able to parse properly, for example:
But let's try Pandoc:
$ pandoc -s test.md -f markdown -t markdown
Text text some text \## Heading
Blah blah
Notice the escaped first "#" symbol in the heading.
I wonder if there is a way to avoid it?
--
With kind regards, Andrew Pashkin.
cell phone - +48 (503) 186 952
e-mail -andrew.pashkin-puGfsi27rH1aa/9Udqfwiw@public.gmane.org
--
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/ee3c5844-ba4f-41d4-a68b-acc237996a03%40gmx.co.uk.
[-- Attachment #2.1: Type: text/html, Size: 1889 bytes --]
[-- Attachment #2.2: LMHTDg0Iwae90au1.png --]
[-- Type: image/png, Size: 38111 bytes --]
next reply other threads:[~2023-11-23 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 17:32 'Andrew Pashkin' via pandoc-discuss [this message]
[not found] ` <ee3c5844-ba4f-41d4-a68b-acc237996a03-puGfsi27rH1aa/9Udqfwiw@public.gmane.org>
2023-11-24 13:48 ` Bastien DUMONT
2023-11-24 13:54 ` John MacFarlane
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=ee3c5844-ba4f-41d4-a68b-acc237996a03@gmx.co.uk \
--to=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).