emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Jason Ross <jasonross1024@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Best way to include METAPOST in ConTeXt exporter
Date: Tue, 05 Oct 2021 00:46:08 +0800	[thread overview]
Message-ID: <87o884buwf.fsf@localhost> (raw)
In-Reply-To: <CABcgBK+RdcGreiPSgcBQ6xEnDmsMACSp3HWj+Zj--07sg4asxg@mail.gmail.com>

Jason Ross <jasonross1024@gmail.com> writes:

> I had considered using special blocks; they match my mental model the best.
> However, they don't provide any support for syntax highlighting or opening
> the block in a new major mode buffer. I'm not sure if it's worth giving up
> language features in order to use the block that's most intuitive to users.
> I'm also considering writing an Org Babel module for METAPOST. This could
> allow METAPOST figures to be included with any export backend. However,
> if I go this route, there are still some challenges:

If you are in control of the export backend, you can directly process
the metapost source blocks during export and ignore/filter their output
as needed.

>    #+MACRO: conditional-header (eval (when (not (eq
> org-export-current-backend 'context)) (concat  "#+HEADER: :results
> file :file " $1)))

>    #+BEGIN_SRC metapost :results drawer :post
> wrap_metapost(name="my-name", caption="my-caption", data=*this*)

Or you can use "raw" results by default and format everything as you
wish in your Org Babel module programatically.

If above is not sufficient, you can install global export filters that
can transform the metapost blocks/source blocks/their results as you
need in other export backends.


  reply	other threads:[~2021-10-04 16:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-03 17:53 Best way to include METAPOST in ConTeXt exporter Jason Ross
2021-10-04  8:41 ` Ihor Radchenko
2021-10-04 15:41   ` Jason Ross
2021-10-04 16:46     ` Ihor Radchenko [this message]
2021-10-05 14:40       ` Jason Ross
2021-10-05 19:50         ` Jason Ross
2021-10-13  6:51           ` Ihor Radchenko
2021-10-13  6:54         ` Ihor Radchenko

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=87o884buwf.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jasonross1024@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).