emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: "Juan Manuel Macías" <maciaschain@posteo.net>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: Way to mark contents of an Org special block as verbatim?
Date: Thu, 6 Jan 2022 14:46:41 -0500	[thread overview]
Message-ID: <CAFyQvY3nn-hOuLs=_S4G5+TFGVBoiihUgdoPP6TTCFjUiSH=qA@mail.gmail.com> (raw)
In-Reply-To: <877dbcwtf7.fsf@posteo.net>

On Thu, Jan 6, 2022 at 2:33 PM Juan Manuel Macías
<maciaschain@posteo.net> wrote:
> I just realized that there is a much simpler solution for your katex
> environment :-)
>
> You can use an example block, and define your custom environment using
> the attribute :environment

Sorry, but this exporter is derived from md, and before exporting the
verbatim body of the special block needs to be surrounded with some
special syntax, with some optional stuff that the user specifies. Also
it could any special block name:
- katex
- tikz
- tikzjax

In any case, if user has this in Org:

#+begin_FOO
<body verbatim>
#+end_FOO

I need to export:

{{< FOO custom stuff >}}
<body verbatim>
{{< /FOO >}}


  reply	other threads:[~2022-01-06 19:48 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 [this message]
2022-01-08 21:52         ` Berry, Charles
2022-01-08 23:29           ` Kaushal Modi
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

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFyQvY3nn-hOuLs=_S4G5+TFGVBoiihUgdoPP6TTCFjUiSH=qA@mail.gmail.com' \
    --to=kaushal.modi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=maciaschain@posteo.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).