From: Sebastian Rose <sebastian_rose@gmx.de>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: minted for latex source code export
Date: Sat, 07 Aug 2010 14:26:28 +0200 [thread overview]
Message-ID: <87pqxu7gnf.fsf@gmx.de> (raw)
In-Reply-To: <87zkwzn9tw.fsf@stats.ox.ac.uk> (Dan Davison's message of "Fri, 06 Aug 2010 09:34:51 -0400")
Dan Davison <davison@stats.ox.ac.uk> writes:
> Seb's nice listings code led me to come across this[1] blog post,
> describing the latex package "minted"[2]. I've made a first-pass
> implementation of org-mode latex export using minted. This didn't take
> too long because I copied the original work Eric Schulte did on
> listings. I think that minted may be an improvement over using listings
> for exporting code from org-mode.
>
> This pdf shows an example of export from org-mode
>
> http://www.princeton.edu/~ddavison/software/org-minted/minted.pdf
>
> My patch is below and in branch "minted" at
> http://github.com/dandavison/org-devel.
>
> minted does coloured syntax highlighting in ~150 languages. Unlike with
> the latex listings package, no extra configuration is required to set up
> the colors and fonts for different language elements. There are other
> nice features such as displaying latex code in code comments, support
> for unicode in the code, and (apparently) greater sophistication of the
> syntax highlighters than the listings package. It uses a python library
> pygments[3] to do the syntax highlighting, so imposes a requirement on
> org users.
Hm --- the listings package comes with TexLive so no extra installation
is neccessary on many systems. And you can define your own languages.
But no configuration of the documents is nice, too :)
Sebastian
next prev parent reply other threads:[~2010-08-08 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 13:34 minted for latex source code export Dan Davison
2010-08-07 7:20 ` Carsten Dominik
2010-08-07 12:26 ` Sebastian Rose [this message]
2010-10-04 7:51 ` Carsten Dominik
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=87pqxu7gnf.fsf@gmx.de \
--to=sebastian_rose@gmx.de \
--cc=davison@stats.ox.ac.uk \
--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
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).