public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: perro tuerto <nika.zhenya-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Code blocks in RST -> Markdown
Date: Fri, 17 Feb 2023 11:33:30 -0800 (PST)	[thread overview]
Message-ID: <6e7992b3-35a1-498b-a2ff-d136d7a96e95n@googlegroups.com> (raw)


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

Hi, I am trying to understand why the following code block in RST is not 
working when I exported it to MD:

.. code:: sh

   echo "Hi"

The result that I get is this one:

.. code:: sh

echo "Hi"

The native is this:

Para
    [ Str ".." , Space , Str "code::" , Space , Str "sh" ]
, Para
    [ Str "echo" , Space , Quoted DoubleQuote [ Str "Hi" ] ]

Also, if I do the inverse (MD -> RST), I actually get the syntax, for 
example:

``` sh
echo "Hi"
```

Gets:

.. code:: sh

   echo "Hi"

So it is RST -> MD the one that is showing an unexpected behavior for me.

What am I doing wrong? I also tried code-block instead of code.

Thanks


-- 
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/6e7992b3-35a1-498b-a2ff-d136d7a96e95n%40googlegroups.com.

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

             reply	other threads:[~2023-02-17 19:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 19:33 perro tuerto [this message]
     [not found] ` <6e7992b3-35a1-498b-a2ff-d136d7a96e95n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-17 19:52   ` perro tuerto

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=6e7992b3-35a1-498b-a2ff-d136d7a96e95n@googlegroups.com \
    --to=nika.zhenya-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).