emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: James Harkins <jamshark70@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: Beamer handouts, pgfpages, no love
Date: Mon, 17 Jun 2013 16:26:41 +0200	[thread overview]
Message-ID: <87txkwizj2.fsf@gmail.com> (raw)
In-Reply-To: <871u815h4e.wl%jamshark70@dewdrop-world.net> (James Harkins's message of "Mon, 17 Jun 2013 15:30:25 +0800")

Hello,


James Harkins <jamshark70@gmail.com> writes:

> Today I was playing around with exporting a beamer presentation for
> handouts, following the advice online to use pgfpages for saving dead
> trees. I'm not sure if it's an org problem or a LaTeX problem.
>
> Exporting to a presentation is no problem:
>
> #+startup: beamer
> #+LaTeX_CLASS: beamer
> #+LaTeX_CLASS_OPTIONS: [presentation]
> #+BEAMER_THEME: default
>
> For handouts, I tried changing it like this:
>
> #+startup: beamer
> #+LaTeX_CLASS: beamer
> #+LaTeX_CLASS_OPTIONS: [handout]
> #+BEAMER_THEME: default
> #+LATEX_HEADER: \usepackage{pgfpages}
> #+LATEX_HEADER: \pgfpagesuselayout{2 on 1}[a4paper,border shrink=5mm]
>
> One problem: if I use any :BMCOL: tags, I get strange errors like this:
>
> ! LaTeX Error: \begin{minipage} on input line 117 ended by \end{altenv}.
>
> ... where the entity that is \ended could be several different things.

An ECM could be useful. By the way, does the generated LaTeX code look
wrong?


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-06-17 14:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17  7:30 Beamer handouts, pgfpages, no love James Harkins
2013-06-17 14:26 ` Nicolas Goaziou [this message]
     [not found]   ` <CAFniQ7X_-m=SYTc1_jQDteAqVhy_e1qMvEgFsCbkHS77EnByBw@mail.gmail.com>
     [not found]     ` <87d2r3sv1c.fsf@gmail.com>
2013-06-30 12:58       ` James Harkins

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=87txkwizj2.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jamshark70@gmail.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).