From: Nick Dokos <nicholas.dokos@hp.com>
To: Ista Zahn <istazahn@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: latex export R code syntax highlighting with minted
Date: Fri, 16 Mar 2012 17:47:14 -0400 [thread overview]
Message-ID: <7779.1331934434@alphaville> (raw)
In-Reply-To: Message from Ista Zahn <istazahn@gmail.com> of "Fri, 16 Mar 2012 16:36:38 EDT." <CA+vqiLFEeYqy9gL4sfMCR+Fs77SVUS=v_s5Q8p9=kHhC==gkSw@mail.gmail.com>
Ista Zahn <istazahn@gmail.com> wrote:
> Hi all,
>
> I'm having trouble modifying the example at
> http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-3
> to highlight R code blocks. The trouble seems to be that org-mode
> identifies R blocks using uppercase R, while pygments looks for
> lowercase r.
>
> For example, org exports
>
> \begin{minted}{R}
> 2+2
> \end{minted}
>
> but pygments doesn't know how to highlight R. If I change to
>
> \begin{minted}{r}
> 2+2
> \end{minted}
>
> (note the lower case r) then it works, but of course I don't want to
> have to perform a find-and-replace every time.
>
> Do you know how to either a) make org-mode identify R blocks with a
> lowercase r, or b) make pygments recognize uppercase R, or c) some
> other solution I've overlooked?
>
Christophe provided the org solution a) and obviously that's the way to go
(maybe one of you could provide a patch to change the default value of
org-export-latex-minted-langs to add the R setting?)
For completeness, and of theoretical interest only, here's how to do b).
o Find the directory where pygments is installed. I just started python
imported pygments and asked for help:
,----
| $ python
| Python 2.7.1+ (r271:86832, Apr 11 2011, 18:13:53)
| [GCC 4.5.2] on linux2
| Type "help", "copyright", "credits" or "license" for more information.
| >>> import pygments
| >>> help(pygments)
| Help on package pygments:
|
| NAME
| pygments
|
| FILE
| /usr/lib/python2.7/dist-packages/pygments/__init__.py
| ...
`----
o cd /path/to/pygments/lexers, edit the file math.py (you probably have
to be root) and add the 'R' alias for 'S':
,----
| ...
| name = 'S'
| aliases = ['splus', 's', 'r', 'R']
| filenames = ['*.S', '*.R']
| mimetypes = ['text/S-plus', 'text/S', 'text/R']
| ...
`----
o run (as root) the _mapping.py script to regenerate stuff:
,----
| $ sudo python _mapping.py
`----
Nick
prev parent reply other threads:[~2012-03-16 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 20:36 latex export R code syntax highlighting with minted Ista Zahn
2012-03-16 21:13 ` Christophe Pouzat
2012-03-16 21:39 ` Ista Zahn
2012-03-16 21:47 ` Nick Dokos [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:
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=7779.1331934434@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=istazahn@gmail.com \
/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).