From: Benjamin Slade <email@example.com>
Subject: Re: orgmode/beamer - won't export blocks
Date: Mon, 30 May 2011 11:18:42 -0500 [thread overview]
Message-ID: <BANLkTi=EmTMCmPiXCWbYdZ7Tib-Ka--eWQ@mail.gmail.com> (raw)
Many thanks for your reply. One last question: do you have an example
(or a link to an explanation about) making one's "own theme"? (I
understand the #+INCLUDE option).
> Message: 20
> Date: Mon, 30 May 2011 16:42:03 +0200
> From: "Sebastien Vauban" <firstname.lastname@example.org>
> To: email@example.com
> Subject: Re: [O] orgmode/beamer - won't export blocks
> Message-ID: <firstname.lastname@example.org>
> Content-Type: text/plain; charset=utf-8
> Hi Benjamin,
> Benjamin Slade wrote:
>> So you don't include LaTeX packages that you always want to be loaded in the
>> .emacs config?
> No, I tend to avoid doing such. This really is the worst place to think of...
> because your .emacs file is personal. Then, you cannot (easily) share any of
> your custom with anybody...
>> 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.
> If you want to do so, either put your list of packages
> - in an Org file that you #+INCLUDE as needed, or
> - in your own theme (that's what I generally end up doing).
> Both are better places, IMHO, for customs.
> Best regards,
next reply other threads:[~2011-05-30 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 16:18 Benjamin Slade [this message]
2011-05-30 17:44 ` orgmode/beamer - won't export blocks Sebastien Vauban
-- strict thread matches above, loose matches on Subject: below --
2011-05-29 17:06 Benjamin Slade
2011-05-30 14:42 ` 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).