emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: orgmode/beamer - won't export blocks
Date: Fri, 27 May 2011 23:35:11 +0200	[thread overview]
Message-ID: <80aae7hlo0.fsf@somewhere.org> (raw)
In-Reply-To: BANLkTinXK-X4cEcHewtydi6aD5jPRYLoqA@mail.gmail.com

Hi Benjamin,

Benjamin Slade wrote:
> Thank you for the help.
> Yes, removing the configuration code from .emacs results in the
> correct behaviour (i.e. blocks are now exported properly).

Where did you find that way to do?  I guess in old threads... Is it still on
Worg, this should be removed.

> Quick question -- is there still a way of setting up beamer/orgmode
> configuration in .emacs?

Why are you asking that?  It's even better: you don't need any special
configuration anymore (like before) for beamer to work out of the box.

The only lines I still have in my .emacs about beamer are:

#+begin_src emacs-lisp
        ;; XXX 2010-03-25 TEMP Fix for conflict TikZ/hyperref: loading
        ;; `atbegshi' before document class beamer
        (add-to-list 'org-export-latex-classes

Maybe even not needed anymore...

Best regards,

Sébastien Vauban

  reply	other threads:[~2011-05-27 21:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25  0:05 orgmode/beamer - won't export blocks Benjamin Slade
2011-05-27  7:01 ` Eric S Fraga
2011-05-27 17:20   ` Benjamin Slade
2011-05-27 21:35     ` Sebastien Vauban [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-05-30 16:18 Benjamin Slade
2011-05-30 17:44 ` Sebastien Vauban
2011-05-29 17:06 Benjamin Slade
2011-05-30 14:42 ` Sebastien Vauban
2011-05-24 17:21 Benjamin Slade
2011-05-24 19:43 ` Sebastien Vauban
2011-05-24 21:11   ` Eric S Fraga

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=80aae7hlo0.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).