Hi Rainer,
Rainer M Krug writes:
> Now this explains it - thanks a million - works absolutely perfectly.
>
> Could that info be added to worg or even the org manual? It mentions the
> listings and color package are mentioned, but not that colors need to be
> specified to have colors in the resul
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 highlig
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 :re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/09/10 10:28, Steven Delean wrote:
> Hi Rainer,
>
> Yes, you will need to provide arguments to the \lstset listings variable
> (i.e. add these arguments to a #+BEAMER_HEADER_EXTRA: line). Below are
> the subset of arguments that I am using so far
Hi Rainer,
Yes, you will need to provide arguments to the \lstset listings variable
(i.e. add these arguments to a #+BEAMER_HEADER_EXTRA: line). Below are
the subset of arguments that I am using so far, though greater
customisation is available (see listings.pdf
www.ctan.org/tex-archive/macros/lat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/09/10 09:31, Steven Delean wrote:
> 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 sourc
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
