From: Kaushal Modi <email@example.com>
To: "Berry, Charles" <firstname.lastname@example.org>
Cc: "Juan Manuel Macías" <email@example.com>,
Subject: Re: Way to mark contents of an Org special block as verbatim?
Date: Sat, 8 Jan 2022 18:29:10 -0500 [thread overview]
Message-ID: <CAFyQvY1UhuV9qZA_f9W=_dgusxgFOfg+P2GH95yvBd_2FueUUQ@mail.gmail.com> (raw)
> What am I missing?
> It seems like you want your derived backend to transcode special blocks somewhat differently than the parent backend. And adding a special block export filter doesn't quite do the job.
I tried out the example Juan posted and it works perfectly well. But
it would require to user to do something similar for each arbitrary
new special block they need. E.g. #+being_katex, #+begin_tikz,
#+begin_tikzjax (could be anything!) where the content needs to be
> For that purpose, you should write a special block transcoder - perhaps falling back to the parent backend for block types you do not wish to handle as described above.
Can you please point me to an example?
> Block specific customizations could rely on a backend specific attribute.
Yes, I am doing block-specific customization (like support
#+attr_shortcode above special blocks here). But I don't know how
to get back the original content of the special block because the
`contents` arg received by the exporter's org-hugo-special-block
already has the Org entities, and sub/super replacements done.
next prev parent reply other threads:[~2022-01-08 23:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 17:00 Way to mark contents of an Org special block as verbatim? Kaushal Modi
2022-01-06 18:27 ` Juan Manuel Macías
2022-01-06 19:14 ` Kaushal Modi
2022-01-06 19:33 ` Juan Manuel Macías
2022-01-06 19:46 ` Kaushal Modi
2022-01-08 21:52 ` Berry, Charles
2022-01-08 23:29 ` Kaushal Modi [this message]
2022-01-09 3:01 ` Berry, Charles
2022-01-09 4:03 ` Kaushal Modi
2022-01-09 16:58 ` Kaushal Modi
2022-01-09 19:57 ` Berry, Charles
2022-01-09 20:01 ` Nicolas Goaziou
2022-01-09 21:53 ` Kaushal Modi
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).