From: Nick Dokos <nicholas.dokos@hp.com>
To: Spike Spiegel <fsmlab@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: questions about exporting to latex using beamer documentclass
Date: Sun, 05 Jul 2009 11:38:05 -0400 [thread overview]
Message-ID: <18486.1246808285@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Spike Spiegel <fsmlab@gmail.com> of "Sun, 05 Jul 2009 12:52:32 BST." <ab777dfe0907050452h5e8c6e3ep539843847768eaca@mail.gmail.com>
Spike Spiegel <fsmlab@gmail.com> wrote:
> ...
> I did some more work last night and came across another issues:
> - #BEGIN_VERBATIM won't work because to use the \begin{verbatim}
> environment the \being{frame} requires [fragile]
>
I worked around this when working on my presentation by putting verbatim stuff
in a file and using \verbatiminput:
,----
| #+LaTeX_CLASS: beamer
| #+TITLE: Example presentation
| #+AUTHOR: Nick Dokos \\ $<$\href{mailto:nicholas.dokos@hp.com}{nicholas.dokos@hp.com}$>$
| #+EMAIL: nicholas.dokos@hp.com
| #+OPTIONS: toc:nil H:2
| #+LaTeX_HEADER: \titlegraphic{\includegraphics{foo.png}}
| * Why \includegraphics[width=5cm]{foo.png}
| ** Reason 1.
| Text explaining reason #1.
| ** Reason 2.
| ... more explanations.
| ** Reason 3.
| Blah, blah, blah.
|
| ** Reason 4.
| Why not?
|
| * What
| ** First piece.
| #+LaTeX: \verbatiminput{foo.1}
| ** Second piece.
| #+LaTeX: \verbatiminput{foo.2}
| ** Third piece.
| ** Fourth piece.
`----
HTH,
Nick
next prev parent reply other threads:[~2009-07-05 15:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fsmlab@gmail.com>
2009-07-04 23:31 ` questions about exporting to latex using beamer documentclass Spike Spiegel
2009-07-05 1:34 ` Nick Dokos
2009-07-05 3:40 ` Nick Dokos
2009-07-05 11:52 ` Spike Spiegel
2009-07-05 15:24 ` Nick Dokos
2009-07-05 15:38 ` Nick Dokos [this message]
2009-07-05 16:40 ` Nick Dokos
2009-07-06 16:24 ` Carsten Dominik
2009-07-05 21:25 ` Russell Adams
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=18486.1246808285@gamaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=fsmlab@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).