emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: Way to mark contents of an Org special block as verbatim?
Date: Thu, 06 Jan 2022 18:27:10 +0000	[thread overview]
Message-ID: <87ee5kwwht.fsf@posteo.net> (raw)
In-Reply-To: <CAFyQvY1d+hySaAMnNg=CWTWSDstqH_qOMAUxzffrdi+eVMhK2A@mail.gmail.com> (Kaushal Modi's message of "Thu, 6 Jan 2022 12:00:31 -0500")

Hi Kaushal,

Kaushal Modi writes:

> I would like to treat that block /like/ how Org treats the latex
> environment blocks, but it needs to be a special block as
> begin_katex/end_katex here is special and it could be a different
> equation rendering backend for another user.
> So is that a header switch or arg that can be passed on to this
> special block that enables the verbatim mode (prevent Org from
> replacing the Org entities, do the sub/superscript expansion, etc.)?

I think one possibility would be using a parse tree export filter:

#+BIND: org-export-filter-parse-tree-functions (katex-verbatim)
#+begin_src emacs-lisp :exports results :results none
  (defun katex-verbatim (tree backend info)
    (when (org-export-derived-backend-p backend 'latex)
      (org-element-map tree 'special-block
	(lambda (block)
	  (when (equal "katex" (org-element-property :type block))
	    (let ((cont (org-element-interpret-data (org-element-contents block)))
		  (create-export-snippet ;; idea from Nicolas Goaziou
		   (lambda (v)
		     (org-element-create 'export-snippet (list :back-end "latex" :value v)))))
	      (apply #'org-element-set-contents
		     (list (funcall create-export-snippet cont))))))

E = -J \sum_{i=1}^N s_i s_{i+1}


E = -J \sum_{i=1}^N s_i s_{i+1}

Best regards,

Juan Manuel 

  reply	other threads:[~2022-01-06 19:11 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 [this message]
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
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:

  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=87ee5kwwht.fsf@posteo.net \
    --to=maciaschain@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaushal.modi@gmail.com \


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