emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: Douglas Bates <bates@stat.wisc.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [babel] configuring LaTeX exports verbatim environment for exported code and results
Date: Tue, 31 Aug 2010 08:40:58 -0600	[thread overview]
Message-ID: <87pqwy975x.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTikO+3dSB3FJf7dV+bvnKX3XTuzw8b1ARBAewG=S@mail.gmail.com> (Douglas Bates's message of "Tue, 31 Aug 2010 08:28:19 -0500")

Hi Douglas,

Douglas Bates <bates@stat.wisc.edu> writes:

> On Tue, Aug 31, 2010 at 8:08 AM, Douglas Bates <bates@stat.wisc.edu> wrote:
>> I have been unable to find in the documentation whether the verbatim
>> environment created by LaTeX exports of source code blocks can be
>> configured.
>>

It is possible to export code using the LaTeX listings package.  See
`org-export-latex-listings'
,----
| org-export-latex-listings is a variable defined in `org-latex.el'.
| Its value is t
| 
| Documentation:
| Non-nil means export source code using the listings package.
| This package will fontify source code, possibly even with color.
| If you want to use this, you also need to make LaTeX use the
| listings package, and if you want to have color, the color
| package.  Just add these to `org-export-latex-packages-alist',
| for example using customize, or with something like
| 
|   (require 'org-latex)
|   (add-to-list 'org-export-latex-packages-alist '("" "listings"))
|   (add-to-list 'org-export-latex-packages-alist '("" "color"))
| 
| You can customize this variable.
| 
| [back]
`----

>>
>> Exporting to LaTeX a section like
[...]
>>
>> Because both the source and the results are presented in verbatim, I
>> don't have much control over the appearance of the code on the slide.
>> If I could, for example, configure the names of the exported
>> environment for the source code and for the results separately, I
>> could use LaTeX's fancyvrb.sty to adjust font sizes, colors, boxes,
>> etc.
>

Listings gives good control over the look of code on a slide, I
generally use the following as my jumping off point for listings style
in Beamer presentations
--8<---------------cut here---------------start------------->8---
#+begin_LaTeX
  \definecolor{dkgreen}{rgb}{0,0.5,0}
  \definecolor{dkred}{rgb}{0.5,0,0}
  \definecolor{gray}{rgb}{0.5,0.5,0.5}
  \lstset{basicstyle=\ttfamily\bfseries\footnotesize,
    morekeywords={virtualinvoke},
    keywordstyle=\color{blue},
    ndkeywordstyle=\color{red},
    commentstyle=\color{dkred},
    stringstyle=\color{dkgreen},
    numbers=left,
    numberstyle=\ttfamily\tiny\color{gray},
    stepnumber=1,
    numbersep=10pt,
    backgroundcolor=\color{white},
    tabsize=4,
    showspaces=false,
    showstringspaces=false,
    xleftmargin=.23in
  }
#+end_LaTeX
--8<---------------cut here---------------end--------------->8---

>
> I just realized that if the code and results are wrapped in other than
> the verbatim environment the org-beamer-fragile-re variable will need
> to be customized.

No, I believe this works with listings blocks out of the box.

> (By the way, automatically detecting the need for the fragile option
> is a great idea.)
>
>> Also, the blank lines before and after the verbatim environment are
>> problematic.  In plain text it makes sense to delimit code chunks with
>> blank lines but in LaTeX a blank line starts a new paragraph and you
>> don't always want that.
>>

You can manually place the #+results line anywhere in the org-mode file
(even immediately after the code block), however it seems the blank
lines still appear in the exported tex file.  This appears to be an
issue with the LaTeX exporter in general rather than Code blocks in
particular.

>>
>> As this is my first posting please let me know if I have
>>inadvertently violated conventions of the list.
>

Looks good to me.

Cheers -- Eric

>
> Well, other than my cut-and-paste glich below :-/
>>
>> Also, the exports append blank lines
>>
>
> _______________________________________________
> 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

      reply	other threads:[~2010-08-31 14:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31 13:08 [babel] configuring LaTeX exports verbatim environment for exported code and results Douglas Bates
2010-08-31 13:28 ` Douglas Bates
2010-08-31 14:40   ` Eric Schulte [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=87pqwy975x.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=bates@stat.wisc.edu \
    --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 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).