emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: hindiogine@gmail.com
Cc: emacs-org <emacs-orgmode@gnu.org>
Subject: Re: Org-beamer problems
Date: Thu, 20 Jan 2011 08:57:07 +0000	[thread overview]
Message-ID: <878vyg6jh8.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87y66gjzyp.fsf@gmail.com> (Henri-Paul Indiogine's message of "Wed, 19 Jan 2011 14:22:38 -0800")

Henri-Paul Indiogine <hindiogine@gmail.com> writes:

> Greetings!
>
> I am also having difficulties running Beamer from org-mode.   I am
> running a fully updated Ubuntu with snapshot emacs and a daily updated
> git version of org-mode.
>
> I am not able to get blocks, lists, and colums to work.  I have a
> feeling from Googling quite a bit that the problem is due to some
> interaction between my org-mode header and .emacs.
>
> Unfortunately, the org-mode manual does not state how to configure
> .emacs for Beamer export.  There must be something going on with the
> levels of headers and the B_Block directive.  

You do not need to configure anything for beamer support with recent
(since 7.0 but even earlier) versions of org.

> Here is the relevant part of my .emacs
>
> -------------------------------------------------
> (setq org-export-latex-classes 

[...]

> 	("beamer" "\\documentclass[bigger]{beamer}

This is not needed and will in fact cause problems.  The tutorial
example on Worg should work out of the box except for the already
discussed problems with the @ syntax for alerts.

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.4 (release_7.4.223.g71650)

  parent reply	other threads:[~2011-01-20 10:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19  7:03 Org-beamer problems Bill Moran
2011-01-19 15:55 ` Jeff Horn
2011-01-19 22:22   ` Henri-Paul Indiogine
2011-01-19 22:33     ` Chris Malone
2011-01-20  8:57     ` Eric S Fraga [this message]
     [not found] ` <AANLkTi=7TkcFBVGc90SkTBHFjKx5j7PgHbia=ZkNRxYS@mail.gmail.com>
2011-01-19 15:58   ` John Hendy
2011-01-19 16:36 ` Eric S Fraga
2011-01-19 21:34   ` Bill Moran
2011-01-19 22:02     ` Chris Malone
2011-01-19 22:43       ` Bill Moran
2011-01-19 22:48         ` Chris Malone
2011-01-20  8:54         ` Eric S Fraga
2011-01-20 19:33           ` Henri-Paul Indiogine
2011-01-21  9:05             ` Eric S Fraga
2011-01-20 21:12           ` Bill Moran
2011-01-21 18:57           ` Henri-Paul Indiogine
2011-01-21 20:54             ` Eric S Fraga
2011-01-21 21:25               ` Henri-Paul Indiogine
2011-01-21 23:39                 ` Eric S Fraga
2011-01-19 22:20     ` Jeff Horn
2011-01-20  8:52     ` Eric S Fraga
  -- strict thread matches above, loose matches on Subject: below --
2011-01-21  2:31 Bill Moran
2011-01-21 21:11 ` Eric S Fraga
2011-01-21 22:29   ` Bill Moran
2011-01-21 23:25   ` Eric S Fraga
2011-01-22  2:52     ` Bill Moran

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=878vyg6jh8.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=hindiogine@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).