From: Carsten Dominik <carsten.dominik@gmail.com>
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, 7 Aug 2010 09:20:27 +0200 [thread overview]
Message-ID: <7868C3EE-18F0-4DF4-8E1E-B971C566AC56@gmail.com> (raw)
In-Reply-To: <87zkwzn9tw.fsf@stats.ox.ac.uk>
Hi Dan,
Looks good!
- Carsten
On Aug 6, 2010, at 3:34 PM, Dan Davison wrote:
> 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.
>
> Below is the org source for the pdf, with instructions for installing
> minted and pygments, and the necessary elisp configuration.
>
> Dan
>
> --8<---------------cut here---------------start------------->8---
> #+title: latex export with minted
>
> This demonstrates export using the [[http://code.google.com/p/
> minted/][minted]] package. minted is a latex
> package that formats source code with syntax highlighting. It uses the
> python library [[http://pygments.org/][pygments]] to do the syntax
> highlighting.
>
> The org-mode patch is in branch =minted= at
>
> git://github.com/dandavison/org-devel.git.
>
> You will also need to get minted.sty, and the python package (see
> requirements). Then, using the =minted= branch of org-mode, make the
> elisp customizations in the Org config section. The source code blocks
> in this file can then be exported to pdf as usual with e.g. C-c C-e d.
>
> * Requirements
> #+begin_src sh
> # Clone minted
> hg clone https://minted.googlecode.com/hg/ minted
> # Install the python syntax highlighter
> sudo aptitude install python-pygments
> #+end_src
>
> * Org config
> #+begin_src emacs-lisp :results silent
> (setq org-export-latex-minted t)
> (add-to-list 'org-export-latex-packages-alist '("" "minted"))
> (setq org-latex-to-pdf-process
> '("pdflatex --shell-escape -interaction nonstopmode %s"))
> #+end_src
>
> * Example by the minted author
>
> #+begin_src csharp
> string title = "This is a Unicode \pi in the sky"
> /*
> Defined as $\pi=\lim_{n\to\infty}\frac{P_n}{d}$ where $P$ is the
> perimeter
> of an $n$-sided regular polygon circumscribing a
> circle of diameter $d$.
> */
> const double pi = 3.1415926535
> #+end_src
>
>
> This example originally demonstrated both unicode strings and \LaTeX
> \nbsp
> code in comments. However the unicode \pi in the string isn't working
> for me at the moment, and I've replaced it with backslash pi.
>
> * Sébastian's example
> #+SRCNAME: srcModifyDB2.sql
> #+BEGIN_SRC sql :tangle srcModifyDB.sql
> -- add column `DossierSentToSecteur' (if column does not exist yet)
> IF NOT EXISTS (SELECT *
> FROM INFORMATION_SCHEMA.COLUMNS
> WHERE TABLE_NAME = 'dossier'
> AND COLUMN_NAME = 'DossierSentToSecteur')
> BEGIN
> ALTER TABLE dossier
> ADD DossierSentToSecteur smalldatetime NULL
> END
> GO
> #+END_SRC
>
> * Python
> #+begin_src python
> def tabulate(x):
> # Return dict containing values and counts
> vals = sorted(unique(x))
> return dict(zip(vals, map(lambda(val): x.count(val), vals)))
> #+end_src
>
> * Notes
>
> To list minted language identifiers:
>
> #+begin_src sh
> pygmentize -L lexers
> #+end_src
>
> #+options: toc:nil
> --8<---------------cut here---------------end--------------->8---
>
> <minted.diff>
>
> Footnotes:
>
> [1] http://stackoverflow.com/questions/1966425/source-code-highlighting-in-latex
>
> [2] http://code.google.com/p/minted/
>
> [3] http://pygments.org/
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
- Carsten
next prev parent reply other threads:[~2010-08-08 17:33 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 [this message]
2010-08-07 12:26 ` Sebastian Rose
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7868C3EE-18F0-4DF4-8E1E-B971C566AC56@gmail.com \
--to=carsten.dominik@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.