[Orgmode] [babel] Re: Removing the blank lines between code and results blocks in LaTeX export

[Austin F. Frank]

Professor Bates--

I used org, org-babel, and lme4 to write my PhD dissertation over the
past few months.  Thanks for your continued excellent work, and I'm glad
to see you here.  I look forward to reading the org source of your
beamer presentations!

Sorry that answers haven't been quicker to arrive-- the org-babel folks
are incredibly productive, but there's a lot on their plates.  One way
to get a quicker response to questions about org-babel is to prefix the
subject with a bracketed "babel" label, as I've done in this response.

On Mon, Sep 06 2010, Douglas Bates wrote:

> Recently Dan Davidson posted a patch to suppress the removal of blank
> lines in exported source code.  I have the opposite problem -
> suppression of blank lines added during LaTeX export
>
> ---- snip --- begin org file ----
> * An R example with :exports both
> The following code
> #+begin_src R :exports both :results output
> 2 + 2
> #+end_src
> shows that there are blank lines added between the code and the
> results sections in \LaTeX export.  Is this configurable? In \LaTeX{}
> the blank lines cause a new paragraph which often I don't want.
> --- snip --- end org file ---
>
> Just copy those lines to an org file and export it to LaTeX to see
> what I mean.

I had similar problems while writing my dissertation, and arrived at
this workaround:

--8<---------------cut here---------------start------------->8---
#+BEGIN_SRC R :exports results :results output latex
library(lme4)
fit <- lmer(Reaction ~ Days + (Days | Subject), sleepstudy)
latex(summary(fit)@coefs,
      file = "",
      dec = 3,
      center = "centering",
      caption = "Parameter estimates for reaction time data",
      label = "tab:reaction-mer")
#+END_SRC
--8<---------------cut here---------------end--------------->8---

Hopefully this will tide you over until Eric and Dan get a chance to
look at your example.  I recognize that it does not accomplish your goal
of typesetting your code according to your customizations, but it worked
for me for including results from mer models.  Please forgive the bad
practice of reaching directly into the summary object to print results
;)

> A related issue is the LaTeX environment for the results.  At present
> it is hard-wired in the function org-export-latex-fixed-width in
> org-latex.el to be the verbatim environment.  I would like to
> configure the appearance of the results using the LaTeX package
> fancyvrb and it would be much easier if I could customize the strings
> preceding and following the exported results.  The current strings are
> "\\begin{verbatim}\n" and "\\end{verbatim}\n\n" and, again, the two
> blank lines inserted after the results can be problematic.

I know Dan Davison has been working on using different verbatim
environments for latex export of source code blocks (not results),
having been dissatisfied with the defaults from listings.  I believe he
recently made the minted package available for LaTeX export-- this does
have some python language dependencies, so it still may not be your
answer.  For exporting source code (as opposed to tabular results), I
find the minted syntax highlighting to be very visually appealing.

Dan or Carsten, is it possible that org-export-latex-listings could be
reconfigured so that the package used for source code export in latex is
configurable?  Or does this functionality already exist and I've missed
it?

And, directly to Professor Bates' question, could a similar treatment be
given to the environment that controls export of verbatim regions?

Sorry not to provide a patch, I've got this pesky defense thing on
Monday.

/au

-- 
Austin Frank
http://aufrank.net
GPG Public Key (D7398C2F): http://aufrank.net/personal.asc

pgp3dk1ZbTCCt.pgp
Description: PGP signature