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: Wed, 13 Oct 2021 14:54:31 +0800	[thread overview]
Message-ID: <87fst5s9co.fsf@localhost> (raw)
In-Reply-To: <CABcgBKJmR4yCTFW996efrmBE1D2pb6=2D68yKXByCS6bnqGG4A@mail.gmail.com>

Jason Ross <jasonross1024@gmail.com> writes:

>> Or you can use "raw" results by default and format everything as you
>> wish in your Org Babel module programatically.
> I'm not sure I understand this yet. Would this emit METAPOST code to the
> Org buffer? Ideally, I'd like to emit METAPOST code if the backend is
> `context`, otherwise, emit a file.

A hackish way would be detecting if you are executing code during export
and emitting different results (say, you may look at
org-export-current-backend).  However, it will do nothing when user
specifies :results file


      parent reply	other threads:[~2021-10-13  6:54 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
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 [this message]

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=87fst5s9co.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).