emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: "Elasady, Summer" <sre@stowers.org>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Exporting Code Blocks to PDF
Date: Tue, 22 Apr 2014 19:43:38 -0500	[thread overview]
Message-ID: <CA+M2ft-ccj1svVN-CCk8Yvvicx9dxpSChRAQccUQx0v-=aF=fg@mail.gmail.com> (raw)
In-Reply-To: <CF7C6547.4CF6%sre@stowers.org>

On Tue, Apr 22, 2014 at 6:28 PM, Elasady, Summer <sre@stowers.org> wrote:
> Hello Emacs World-
> I’m using LaTex to export documents to PDF, but the code blocks are not
> fitting to the page properly and the code is being cutoff. Is there a way to
> turn on word-wrapping for export to PDF, or to resize code blocks?

I don't know if there's a way to wrap, but in my one formal
programming class, the convention was only to write 80 characters or
less -- are you exceeding that? If not, and it's just a font size
thing, you can always use LaTeX to reduce the font. I frequently do
this, especially using code in Beamer presentations:

#+latex: \scriptsize
#+begin_src R blah blah

code here

#+latex: \normalsize

This way, the block is downsized, and then resumes to regular font
size for the rest of the document. You can use any size command you
want; I frequently use \footnotesize, \scriptsize, and \tiny. I hardly
notice a difference with \small, though you can try that, too.

> Also, does anyone have a good system for dealing with exporting large
> tables? Right now I’m just linking to a file, but I’m curious if anyone else
> is doing anything clever.

For tables that are /close/ in size already, I do the same thing as
above, at least if we're talking about fitting to width. You can also
flip sideways and extend over multiple pages to handle both wide and

#+latex: \begin{landscape}
#+attr_latex: :environment longtable
| *alpha* | *beta* | *gamma* | *delta* |
|       1 |      1 |       1 |       1 |
|       2 |      2 |       2 |       2 |
|       3 |      3 |       3 |       3 |
|       4 |      4 |       4 |       4 |
#+latex: \end{landscape}

You can use them independently, too. Initially I tried the Org syntax
for sidewaystable, but it didn't seem to work with longtable:
- http://orgmode.org/manual/LaTeX-specific-attributes.html

As in, technically it would seem you could do:

#+attr_latex: :environment longtable :float sidewaystable

But perhaps that's more of a LaTex issue:
- http://tex.stackexchange.com/questions/63585/sidewaystable-together-with-longtable

Anyway, the above works, and that covers any handles I've ever used
(font, rotate, extend over multiple pages). Other than trying to
wordsmith my column names where the title exceeds the contents...
that's all the tricks up my sleeve!


> Thanks in advance!
> Summer
> SRE@stowers.org

  reply	other threads:[~2014-04-23  0:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CF7C6501.4CF3%sre@stowers.org>
2014-04-22 23:28 ` Exporting Code Blocks to PDF Elasady, Summer
2014-04-23  0:43   ` John Hendy [this message]
2014-04-23  7:22     ` Bernhard Pröll

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:

  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='CA+M2ft-ccj1svVN-CCk8Yvvicx9dxpSChRAQccUQx0v-=aF=fg@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sre@stowers.org \


* 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


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).