From: tsd@tsdye.com (Thomas S. Dye)
To: Shiyuan <gshy2014@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: R src block not highlighted in pdf
Date: Fri, 27 Jun 2014 08:39:29 -1000 [thread overview]
Message-ID: <m2egya9oym.fsf@tsdye.com> (raw)
In-Reply-To: <CAOm4EMsMt1T98r_YiRVAMp3P3_oC2UPu7h5c8iH3nOX1OSxUAA@mail.gmail.com> (Shiyuan's message of "Fri, 27 Jun 2014 10:23:33 -0700")
Aloha Shiyuan,
Shiyuan <gshy2014@gmail.com> writes:
> Hi,
> I have a R code src block in a org file. When exported to html, the R
> code is correctly syntax highlighted. But when exported to pdf(latex), the
> R code is not highlighted. I found this thread
> https://lists.gnu.org/archive/html/emacs-orgmode/2010-07/msg00379.html
> <https://lists.gnu.org/archive/html/emacs-orgmode/2010-07/msg00379.html> which
> suggests setting the variable org-export-latex-listings. This variable
> seems no longer exist in Org 8.2.6. What variables shall I set so that the
> R code is syntax highlighted when exported to pdf in Org mode 8.2.6?
> Thanks.
>
> Shiyuan
> Hi,
> I have a R code src block in a org file. When exported to html, the R
> code is correctly syntax highlighted. But when exported to pdf(latex),
> the R code is not highlighted. I found this thread
> https://lists.gnu.org/archive/html/emacs-orgmode/2010-07/msg00379.html
> which suggests setting the variable org-export-latex-listings. This
> variable seems no longer exist in Org 8.2.6. What variables shall I
> set so that the R code is syntax highlighted when exported to pdf in
> Org mode 8.2.6? Thanks.
That variable was renamed org-latex-listings in v. 8.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
prev parent reply other threads:[~2014-06-27 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 17:23 R src block not highlighted in pdf Shiyuan
2014-06-27 18:38 ` Grant Rettke
2014-06-27 21:46 ` Shiyuan
2014-06-27 22:37 ` Nick Dokos
2014-06-29 5:57 ` Shiyuan
2014-06-27 18:39 ` Thomas S. Dye [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=m2egya9oym.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=gshy2014@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).