public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Allen Downey <allendowney-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Markdown writer ignores backtick_code_blocks?
Date: Sun, 24 Jan 2021 07:18:20 -0800 (PST)	[thread overview]
Message-ID: <3001f072-a5fb-450a-9f8c-ba901a31b3c1n@googlegroups.com> (raw)


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

Hi All.  I am using pandoc 2.11 with the following test input:

```
Paragraph

\begin{verbatim}
Code block
Code block
\end{verbatim}

Paragraph
```

Then I translate to Markdown with the following commands:

```
pandoc test.tex -t markdown > test1.md
pandoc test.tex -t markdown+fenced_code_blocks > test2.md
pandoc test.tex -t markdown+backtick_code_blocks > test3.md
```

The result of all three is the same:

```
Paragraph

    Code block
    Code block

Paragraph
```

The code block is indented, which implies that the reader recognizes it as 
a code block.  But the writer seems to ignore the extensions.

Am I doing something wrong here?

Thanks!
Allen

-- 
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/3001f072-a5fb-450a-9f8c-ba901a31b3c1n%40googlegroups.com.

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

             reply	other threads:[~2021-01-24 15:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-24 15:18 Allen Downey [this message]
     [not found] ` <3001f072-a5fb-450a-9f8c-ba901a31b3c1n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-01-24 18:07   ` John MacFarlane
     [not found]     ` <m2im7mgqdl.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-01-24 18:59       ` Zev Spitz
2021-01-25 15:54       ` Daniel Staal
     [not found]         ` <f7183b34-f20e-2024-34dc-8803de6298e5-Jdbf3xiKgS8@public.gmane.org>
2021-01-25 16:10           ` Allen Downey
2021-01-25 16:47           ` BPJ
     [not found]             ` <CADAJKhCTHtpvmJWpHaZe5hrZMb39Vdzd0kMkSnEOvsjjB9DobA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-01-25 17:29               ` Daniel Staal

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=3001f072-a5fb-450a-9f8c-ba901a31b3c1n@googlegroups.com \
    --to=allendowney-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).