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: Transform a fenced div to mkdocs markdown admonition format
Date: Thu, 3 Nov 2022 13:09:39 -0700	[thread overview]
Message-ID: <7AF275BD-12EB-4424-84E5-1A45FF675520@gmail.com> (raw)
In-Reply-To: <ddc82450-b82b-4b8f-9d5f-30c6a28c206fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

I assume you’re targeting markdown?

You could then just create a RawBlock with format “markdown”, and put this content in it with whatever indentation you like.


> On Nov 3, 2022, at 9:14 AM, Aidan Reilly <aireilly-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
> 
> Hello!
> 
> Trying to figure out how to use pandoc +fenced_div with a filter to transform this:
> 
> ::: note
> Here is the first line of this note.
> 
> And the second,
> 
> And the third!
> :::
> 
> into this:
> 
> !!! note
>     Here is the first line of this note.
> 
>     And the second,
> 
>     And the third!
> 
> Struggling to understand if it is possible to "indent" elements using pandoc. The mkdocs markdown spec requires the body of notes to be indented by 4 spaces.  Is there a way to apply indents without stringifying the content?
> 
> 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/ddc82450-b82b-4b8f-9d5f-30c6a28c206fn%40googlegroups.com.

-- 
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/7AF275BD-12EB-4424-84E5-1A45FF675520%40gmail.com.


  parent reply	other threads:[~2022-11-03 20:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 16:14 Aidan Reilly
     [not found] ` <ddc82450-b82b-4b8f-9d5f-30c6a28c206fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-03 20:09   ` John MacFarlane [this message]
     [not found]     ` <7AF275BD-12EB-4424-84E5-1A45FF675520-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-11-03 20:40       ` Aidan Reilly
     [not found]         ` <CAM4RMsh1iqDjA7WqfCuWJV4NCD_ELXfFL0iV+pGUWASvgAzq5g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-11-03 20:55           ` Aidan Reilly
     [not found]             ` <CAM4RMsj6rwDLDmNxNzvUDODw0qa5NZgZtbAS_ozf+XJ3ZE+jHw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-11-03 21:00               ` Albert Krewinkel
     [not found]                 ` <87h6zf698z.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-04  0:25                   ` Aidan Reilly
     [not found]                     ` <CAM4RMshtHUuFSHryQqAgquMduCd5xSM7c2CKnvR0H1=zsg2xQQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-11-05  8:03                       ` Albert Krewinkel
     [not found]                         ` <87a6556cg2.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-05 13:09                           ` Aidan Reilly
     [not found]                             ` <CAM4RMsiRRywBgcHHQgfUxV5BZQfQw5sgqy44za4VC9=_TmqYPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-11-05 13:10                               ` Aidan Reilly
2022-11-05 13:53                               ` Albert Krewinkel
     [not found]                                 ` <875yft5wqc.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-05 16:26                                   ` Aidan Reilly

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=7AF275BD-12EB-4424-84E5-1A45FF675520@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).