public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Dominik Heinz <domi.hz96-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Process inline codeblocks and normal codeblocks differently when converting from md to html
Date: Sun, 2 May 2021 16:36:46 -0700 (PDT)	[thread overview]
Message-ID: <ca5c7bce-bd16-420e-8e14-274f502207f7n@googlegroups.com> (raw)


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


Hello,

I am using pandoc to convert from markdown to html.
The markdown document I am processing contains both, inline code blocks 
(single `at start and end) and also normal codeblocks (triple ```at start 
and end).
Pandoc wraps both of these in <code></code> tags as to be expected. 
However, since I want to style them differently later with CSS, I need a 
way to differentiate between them. Is there a way to tell pandoc to add a 
class or something like that to the code tag, when its an inline code 
block? 
I didn't find anything in the official documentation on how to achieve this.
Any help is appreciated.

Cheers.

-- 
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/ca5c7bce-bd16-420e-8e14-274f502207f7n%40googlegroups.com.

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

             reply	other threads:[~2021-05-02 23:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-02 23:36 Dominik Heinz [this message]
     [not found] ` <ca5c7bce-bd16-420e-8e14-274f502207f7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-03  0:17   ` jeremy theler
     [not found]     ` <CAK0LiykNeu1wkPP9TsB92OrDK7LNdneicrXFADCU-aR2rbz7Cw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-05-03  6:56       ` Bastien DUMONT

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=ca5c7bce-bd16-420e-8e14-274f502207f7n@googlegroups.com \
    --to=domi.hz96-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).