public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Aidan Reilly <aireilly-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: docbook  codeblock callouts > markdown
Date: Fri, 18 Nov 2022 01:03:23 -0800 (PST)	[thread overview]
Message-ID: <99430384-ef3a-4534-a9da-8dcbcf7f0f91n@googlegroups.com> (raw)


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

H again,

A feature of docbook/asciidoc that is really useful is codeblock callouts. 
It seems that this is not currently supported in the latest pandoc. 

Is there a way to tell pandoc to passthrough codeblocks "untouched"? I 
think if this was the case a lua filter could apply the rest of the markup 
I need. 

Example: 
$ cat callout.adoc
[source,yaml]
----
bmc:
  address: <bmc_address>
  credentialsName: <secret_credentials_name>  <1>
  disableCertificateVerification: True
----
<1> `credentialsName` needs a callout>

Run through asciidoctor > pandoc:
 
$ asciidoctor -b docbook -o - callout.adoc | pandoc -t markdown -f docbook
``` yaml
bmc:
  address: <bmc_address>
  credentialsName: <secret_credentials_name>  
  disableCertificateVerification: True
```

-   `credentialsName` needs a callout

Any other suggestions or strategies welcome

Thanks,
Aidan

-- 
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/99430384-ef3a-4534-a9da-8dcbcf7f0f91n%40googlegroups.com.

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

             reply	other threads:[~2022-11-18  9:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18  9:03 Aidan Reilly [this message]
     [not found] ` <99430384-ef3a-4534-a9da-8dcbcf7f0f91n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-23 17:34   ` Albert Krewinkel
     [not found]     ` <8735a9po3h.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-25 10:24       ` Aidan Reilly
     [not found]         ` <7925cbe1-1d0d-4b9f-abe4-9224472bd417n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-12-01 16:57           ` Aidan Reilly
     [not found]             ` <42d817a7-49f5-452a-a38c-d0764ec3e5cdn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-12-03  8:16               ` Albert Krewinkel
     [not found]                 ` <87tu2cx5k6.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-12-03 10:13                   ` 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=99430384-ef3a-4534-a9da-8dcbcf7f0f91n@googlegroups.com \
    --to=aireilly-h+wxahxf7alqt0dzr+alfa@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).