From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Formatting issue when exporting with LaTeX/Beamer
Date: Fri, 07 Mar 2014 17:06:42 -0500 [thread overview]
Message-ID: <87txb98xzh.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: CF3F4B60.268F%sre@stowers.org
"Elasady, Summer" <sre@stowers.org> writes:
> Hello-
>
> Thanks in advance for any help/advice. I am new to LaTeX and Beamer
> and did not find any documentation on this specific issue.
>
The first piece of advice I have is: don't post screenshots - they are
useless. I can't cut and paste from the screenshot to try to reproduce
the problem, so I would have to type the damn thing in (or as in this
case, hunt around in the links you provided to find something that I can
work with). Why are you making life difficult for the people whose help
you are seeking? Just include your org file directly in the email - see
below for an example.
> I am trying to export to Beamer to create presentations out of my
> OrgMode documents and I’m running into a strange formatting issue. The
> headers are being printed out before any of the content. So my export
> will show all the headers in order, followed by all the content in
> order, instead of exporting header/content, header2/content2, etc.
>
What version of emacs/org are you using? I can't reproduce this ordering
problem, although I do have troubles producing the code listings.
Versions:
Org-mode version 8.2.5h (release_8.2.5h-682-g080f1d @
/home/nick/elisp/org-mode/lisp/)
GNU Emacs 24.3.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.6.4) of
2014-02-28
Here is the org file I used:
--8<---------------cut here---------------start------------->8---
#+MACRO: BEAMERMODE presentation +MACRO: BEAMERTHEME Antibes +MACRO:
#BEAMERCOLORTHEME lily +MACRO: BEAMERSUBJECT RMRF +MACRO:
#BEAMERINSTITUTE Miskatonic University, Astrology Dept. +TITLE:
#Presentation with Org-Mode and Beamer +AUTHOR: Someone
* My presentation
** Overview
1. Introduction
2. Main part
3. Questions
** Some interesting stuff
*** an important point
- subpoint a
- subpoint b
* Another slide
** Graphics
*** a picture
#+begin_src ditaa :file blue.png
+---------+
| cBLU |
| +----+
| |cPNK|
+----+----+
#+end_src
#+RESULTS:
[[file:blue.png]]
*** another picture
#+LaTeX:\includegraphics{emacs.png}
* And another
** More interesting stuff
*** some C++ code
#+begin_LaTeX
\begin{lstlisting}[language=c++] for (int i = 1; i != 10; ++i)
std::cout << i << ": hello, world!"
<< std::endl; \end{lstlisting}
#+end_LaTeX
*** and some Python
#+begin_LaTeX
\begin{lstlisting}[language=python] for i in range(1,10):
print i, "hello, world!" \end{lstlisting}
#+end_LaTeX
--8<---------------cut here---------------end--------------->8---
If I get rid of the code listings, everything works as expected for me.
With the code listings I get this error - no idea why:
,----
| (/usr/share/texlive/texmf-dist/tex/latex/listings/lstlang1.sty)
| (/usr/share/texlive/texmf-dist/tex/latex/listings/lstlang1.sty)
| (/usr/share/texlive/texmf-dist/tex/latex/listings/lstmisc.sty) Overfull
| \hbox (40.77774pt too wide) in paragraph at lines 82--82
| [][]\T1/cmss/m/n/10.95 stlistinglocklocknd some
| Python-stlist-ingstlist-in-gloc k-lock-eamer@frameslideAnd
|
| Package Listings Warning: Text dropped after begin of listing on input
| line 82.
|
|
| )
| ! Emergency stop.
| <*> .../nick/src/org/latex/beamer-presentation.tex
|
| ! ==> Fatal error occurred, no output PDF file produced!
`----
Nick
prev parent reply other threads:[~2014-03-07 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 16:09 Formatting issue when exporting with LaTeX/Beamer Elasady, Summer
2014-03-07 21:30 ` Eric S Fraga
2014-03-07 22:06 ` Nick Dokos [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=87txb98xzh.fsf@alphaville.bos.redhat.com \
--to=ndokos@gmail.com \
--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).