From: Daniel Bausch <bausch@dvs.tu-darmstadt.de>
To: emacs-orgmode@gnu.org
Subject: Re: [dev] About a beamer back-end
Date: Mon, 18 Jun 2012 08:32:19 +0200 [thread overview]
Message-ID: <4FDECB73.5030904@dvs.tu-darmstadt.de> (raw)
In-Reply-To: <87ehpg8vfo.fsf@gmail.com>
Hi Nicolas,
first of all, I think the block idea is a good one, as long a notes will
remain headlines. Nevertheless I often had the problem in my documents,
that I wanted to insert code between frames. It would be great, if you
could provide a clean solution for such things, too. (ignoreheading
does not work in all cases) A special headline class or tag that does
not generate a frame but can contain LaTeX code that is inserted instead
of a frame would be enough. Inserting a great number of "newcommand"
calls before the first frame would be another use of such a thing, as
the alternative, multiple "#+LaTeX_HEADER" statements, is very ugly and
even sometimes fails because of parser problems.
Then I had another problem, for which I was forced to patch the org-mode
code: My university requires me to use a corporate design for my slides.
This design is implemented as a document class, so instead of
\documentclass{beamer} I need to use a different class name. However,
Org Beamer only works correctly, if the documentclass is "beamer".
(#+STARTUP: beamer is NOT enough) Therefore, I needed to change the
hardcoded string in the source code (and now can only output documents
with the corporate style). It would be very nice, if you could find a
solution that works without a hardcoded string at all. Maybe rely on
"#+STARTUP: beamer" or something else. (The function I needed to modify
is org-beamer-after-initial-vars)
Kind regards,
Daniel
--
Daniel Bausch
Wissenschaftlicher Mitarbeiter
Technische Universität Darmstadt
Fachbereich Informatik
Fachgebiet Datenbanken und Verteilte Systeme
Hochschulstraße 10
64289 Darmstadt
Germany
Tel.: +49 6151 16 6706
Fax: +49 6151 16 6229
next prev parent reply other threads:[~2012-06-18 6:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 15:08 [dev] About a beamer back-end Nicolas Goaziou
2012-06-15 16:41 ` suvayu ali
2012-06-15 16:47 ` Avdi Grimm
2012-06-18 7:50 ` Eric S Fraga
2012-06-18 12:35 ` suvayu ali
2012-06-19 13:21 ` Nicolas Goaziou
2012-06-19 21:04 ` Eric S Fraga
2012-06-20 6:23 ` Greg Tucker-Kellogg
2012-06-20 11:55 ` Sebastien Vauban
2012-06-20 15:20 ` Eric S Fraga
2012-06-21 14:37 ` Nicolas Goaziou
2012-06-21 14:51 ` Sebastien Vauban
2012-06-21 16:03 ` Nicolas Goaziou
[not found] ` <87obocodo7.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-06-21 21:14 ` **: " Sebastien Vauban
2012-06-25 22:39 ` Andreas Leha
2012-06-21 14:55 ` Rasmus
2012-06-21 15:56 ` Nicolas Goaziou
2012-06-21 16:36 ` Rasmus
2012-06-21 16:49 ` suvayu ali
2012-06-22 7:54 ` Eric S Fraga
2012-06-18 6:32 ` Daniel Bausch [this message]
2012-06-18 10:17 ` Rasmus
2012-06-18 10:35 ` Sebastien Vauban
2012-06-18 12:00 ` Rasmus
2012-06-28 10:40 ` Andreas Leha
2012-06-28 10:47 ` suvayu ali
2012-06-28 10:50 ` Andreas Leha
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=4FDECB73.5030904@dvs.tu-darmstadt.de \
--to=bausch@dvs.tu-darmstadt.de \
--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).