public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Failed to recognize headers from DevOps wiki missing a leading space
Date: Tue, 22 Nov 2022 14:46:36 -0800	[thread overview]
Message-ID: <923D39E7-49FB-4702-B867-0AAC618B4CF8@gmail.com> (raw)
In-Reply-To: <9798935e-bb5a-4164-a68e-633a198d69ecn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Try with

-f markdown-space_in_atx_header

commonmark doesn't allow headings with no space after #, nor does pandoc with its default settings, but you can disable that extension as above.

> On Nov 22, 2022, at 2:39 PM, Dev Null <dev.null9675234-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> 
> Hi


  parent reply	other threads:[~2022-11-22 22:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 22:39 Dev Null
     [not found] ` <9798935e-bb5a-4164-a68e-633a198d69ecn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-22 22:46   ` John MacFarlane [this message]
     [not found]     ` <923D39E7-49FB-4702-B867-0AAC618B4CF8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-11-23  0:20       ` Dev Null

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=923D39E7-49FB-4702-B867-0AAC618B4CF8@gmail.com \
    --to=fiddlosopher-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).