From: Steven Delean <steven.delean@adelaide.edu.au>
To: emacs-orgmode@gnu.org
Cc: wxhgmqzgwmuf@spammotel.com, Rainer M Krug <r.m.krug@gmail.com>
Subject: Re: Color of exported R code results using LaTeX listings
Date: Sat, 18 Sep 2010 12:09:41 +0930 [thread overview]
Message-ID: <1284777581.3782.17.camel@sduofa-desktop> (raw)
In-Reply-To: <87k4mk5uji.fsf@gmail.com>
Hi Eric, Rainer and Sébastien,
Thanks again for all your assistance. I was not able to achieve the
results I was after exactly using any proposed solutions, but have found
a way forward and outline my solution below in case it benefits others.
The following allows fontification and syntax highlighting for source
code and a single color for exported output, and works both for latex
documents and beamer slides.
NB: A single color for source code in exported documents can be acheived
by adding e.g. \color{blue} to basicstyle.
1. The following must appear in your .emacs
(require 'org-latex)
(setq org-export-latex-listings t)
(add-to-list 'org-export-latex-packages-alist '("" "listings"))
(add-to-list 'org-export-latex-packages-alist '("" "color"))
2. Add the following to your .org document header to allow colors and
'nice' font
#+LATEX_HEADER: \lstset{
#+LATEX_HEADER: keywordstyle=\color{blue},
#+LATEX_HEADER: commentstyle=\color{red},
#+LATEX_HEADER: stringstyle=\color{green},
#+LATEX_HEADER: basicstyle=\ttfamily\small,
#+LATEX_HEADER: columns=fullflexible,
#+LATEX_HEADER: basewidth={0.5em,0.4em}
#+LATEX_HEADER: }
3. Also add the following to your .org document header to allow the
output results of evaluating R (or other language) code to be in color
#+LATEX_HEADER: \RequirePackage{fancyvrb}
#+LATEX_HEADER: \DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=
\small,formatcom = {\color[rgb]{0.5,0,0}}}
Hope it helps,
Regards,
Steve
On Fri, 2010-09-17 at 08:24 -0400, Eric Schulte wrote:
> Hi Steven,
>
> If your R blocks are outputting actual R code, then you can use the
> "code" argument to the :results header argument to have the output
> exported as R code under listings instead of within verbatim blocks.
> --8<---------------cut here---------------start------------->8---
> #+begin_src R :results code 8 #+end_src
>
> #+results:
> #+BEGIN_SRC R
> 8
> #+END_SRC
> --8<---------------cut here---------------end--------------->8---
>
> Alternately if your output is some other language you could use the
> ":results latex" header argument and explicitly provide the listings
> wrapper yourself.
>
> Hope this Helps -- Eric
>
> Steven Delean <steven.delean@adelaide.edu.au> writes:
>
> > Hi everyone,
> >
> > I am using org-mode to make a beamer presentation that includes blocks
> > of R code and wish to export the source code and results to pdf in
> > color (using the listings package).
> >
> > The source code block syntax is highlighted successfully, but the
> > output results of the executed R code are not colored at all.
> >
> > The results are presented in \begin{verbatim}...\end{verbatim},
> > whereas the source code is presented within
> > \begin{lstlisting}...\end{lstlisting}. I can affect changes to the
> > fontsize and color of the source code using \lstset in the .org
> > document header, but not the results output from evaluating the code.
> >
> > Is there some way I can export these results in color?
> >
> > Thanks for any suggestions,
> >
> > Regards,
> > Steve
> >
> > PS I have the follwing in my .emacs
> > (require 'org-latex)
> > (setq org-export-latex-listings t)
> > (add-to-list 'org-export-latex-packages-alist '("" "listings"))
> > (add-to-list 'org-export-latex-packages-alist '("" "color"))
> >
> >
> >
> >
> >
> > _______________________________________________
> > 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
next prev parent reply other threads:[~2010-09-18 2:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 7:31 Color of exported R code results using LaTeX listings Steven Delean
2010-09-17 8:00 ` Rainer M Krug
2010-09-17 8:28 ` Steven Delean
2010-09-17 8:52 ` Sébastien Vauban
2010-09-17 9:13 ` Rainer M Krug
2010-09-17 13:14 ` Steven Delean
2010-09-17 13:20 ` Rainer M Krug
2010-09-17 13:30 ` Sébastien Vauban
2010-09-17 14:15 ` Rainer M Krug
2010-09-17 9:05 ` Rainer M Krug
2011-01-04 10:06 ` Bastien
2010-09-17 12:24 ` Eric Schulte
2010-09-18 2:39 ` Steven Delean [this message]
2010-09-18 7:10 ` Sébastien Vauban
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=1284777581.3782.17.camel@sduofa-desktop \
--to=steven.delean@adelaide.edu.au \
--cc=emacs-orgmode@gnu.org \
--cc=r.m.krug@gmail.com \
--cc=wxhgmqzgwmuf@spammotel.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).