From: Benjamin Slade <firstname.lastname@example.org>
Subject: Re: orgmode/beamer - won't export blocks
Date: Sun, 29 May 2011 12:06:08 -0500 [thread overview]
Message-ID: <BANLkTimMQ2qOCKv9xNvMVrg59ZOGfL8ZkQ@mail.gmail.com> (raw)
So you don't include LaTeX packages that you always want to be loaded
in the .emacs config? I have a bunch of packages that I would need for
my beamer presentations and it would be nice just to have them
automatically included every time.
By the bye, I found the old config code from here:
From: Sebastien Vauban
Subject: Re: [O] orgmode/beamer - won't export blocks
Date: Fri, 27 May 2011 23:35:11 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (windows-nt)
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:
;; XXX 2010-03-25 TEMP Fix for conflict TikZ/hyperref: loading
;; `atbegshi' before document class beamer
Maybe even not needed anymore...
next reply other threads:[~2011-05-29 17:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 17:06 Benjamin Slade [this message]
2011-05-30 14:42 ` orgmode/beamer - won't export blocks Sebastien Vauban
-- 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-25 0:05 Benjamin Slade
2011-05-27 7:01 ` Eric S Fraga
2011-05-27 17:20 ` Benjamin Slade
2011-05-27 21:35 ` Sebastien Vauban
2011-05-24 17:21 Benjamin Slade
2011-05-24 19:43 ` Sebastien Vauban
2011-05-24 21:11 ` Eric S Fraga
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 \
* 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).