From: Dev Null <dev.null9675234-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Failed to recognize headers from DevOps wiki missing a leading space
Date: Tue, 22 Nov 2022 16:20:03 -0800 (PST) [thread overview]
Message-ID: <c88bc4b2-b0f2-4315-901f-8dc711a9dd79n@googlegroups.com> (raw)
In-Reply-To: <923D39E7-49FB-4702-B867-0AAC618B4CF8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1004 bytes --]
Thanks; you're a lifesaver. I needed -blank_before_header as well to get
the DevOps wiki to parse properly, but once I'd looked
up space_in_atx_header, that was easy enough to find.
- rob.
On Wednesday, November 23, 2022 at 11:46:41 AM UTC+13 fiddlosopher wrote:
> 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.nul...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >
> > Hi
>
>
--
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/c88bc4b2-b0f2-4315-901f-8dc711a9dd79n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1652 bytes --]
prev parent reply other threads:[~2022-11-23 0:20 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
[not found] ` <923D39E7-49FB-4702-B867-0AAC618B4CF8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-11-23 0:20 ` Dev Null [this message]
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=c88bc4b2-b0f2-4315-901f-8dc711a9dd79n@googlegroups.com \
--to=dev.null9675234-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).