emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Charles Berry <ccberry@ucsd.edu>
To: emacs-orgmode@gnu.org
Subject: Re: Adding export option for babel language
Date: Thu, 8 May 2014 16:17:23 +0000 (UTC)	[thread overview]
Message-ID: <loom.20140508T180556-884@post.gmane.org> (raw)
In-Reply-To: m2fvklgf80.fsf@gmail.com

Ken Mankoff <mankoff <at> gmail.com> writes:

> 
> 
> I'd like to add support for PythonTeX to Org Babel 
> https://github.com/gpoore/pythontex
> 
> The motivation is that PythonTeX is a better literate environment than
> just Org + Babel, because it can print results inline just like an
> interactive Python session, instead of all the code followed by all the
> results. 
> 
> This is just a modification to the existing LaTeX export for python, it
> is not support for a new language. I'm new to Org development and seek
> advice how to begin approaching the solution.
> 
> I'd like the python code blocks to behave just as they do now, but if I
> have set (setq org-latex-listings 'pythontex) instead of (setq
> org-latex-listings 'minted), then instead of wrapping python code blocks
> with:
> 
> \begin{minted}[]{python}
> x+2
> print x
> \end{minted}
> 
> It should wrap them with
> 
> \begin{pyconsole}
> x+2
> print x
> \end{pyconsole}
> 

A quick-and-dirty approach to do just that much would be to write an export
filter for `src-block' and maybe `inline-src-block', see

   (info "(org) Advanced configuration")

   http://orgmode.org/worg/dev/org-export-reference.html#filter-system

and 

    http://orgmode.org/worg/exporters/filter-markup.html


Also, `C-h f org--filter TAB' should give you a buffer of such filter
functions (and a couple of false positives) that you might browse.


HTH,

Chuck 

next prev parent reply	other threads:[~2014-05-08 16:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08  2:46 Adding export option for babel language Ken Mankoff
2014-05-08 16:17 ` Charles Berry [this message]
2014-05-08 19:53   ` Ken Mankoff
2014-05-08 20:09     ` Ken Mankoff

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=loom.20140508T180556-884@post.gmane.org \
    --to=ccberry@ucsd.edu \
    --cc=emacs-orgmode@gnu.org \
    /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

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