From: Rasmus Pank Roulund <rasmus.pank@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Beamer and non-frames
Date: Sun, 29 May 2011 19:18:19 +0200 [thread overview]
Message-ID: <irtv22$kr$1@dough.gmane.org> (raw)
In-Reply-To: irtubr$voq$1@dough.gmane.org
> I am sorry I have no solution for you just now.
> This behavior you're seeking is something I long for as well, to
> insert a this frame only custom background, to be precise.
So many great things can be put in-between
\end{frame}
...
\begin{frame}
in Beamer....
> The issue lies in the org-beamer.el way of divvying up the file into
> frames (if memory servers me, it's the org-beamer-sectioning function,
> but I can be mistaken), it's a big function that handles most of
> org-beamers functionality. For the behavior that we seek we need to
> implement a function that can encapsulate the \begin{frame}
> ... \end{frame} code. However, this is not trivial.
Yeah, I gussed it was something like that..
However, maybe something like to the following could be implemented.
I note the following in my file:
** Frame
...
#+latex_beamer_outside_frame: \againframe<2>{overview.fig} %(1)
** Next frame
The 'Org-exporter' notices (1) and stores it in a list L. Each time it
writes \end{frame} it also checks L and if L is non-empty the exporter
will dump whatever currently exists in L after \end{frame}.
I do, however, not know whether this is easily implemented.
> It has my interest, but don't expect anything useful from me in the
> short term, as I am an elisp noob and I am just getting acquainted
> with the org api.
I am neither good at lisp nor programming in general, although I do need
the command for a Python presentation. I guess I'll have to fix the Beamer
code 'by hand'.
–Rasmus
--
Sent from my Emacs
next prev parent reply other threads:[~2011-05-29 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 8:36 Beamer and non-frames Rasmus Pank Roulund
2011-05-29 17:04 ` Sander Boer
2011-05-29 17:18 ` Rasmus Pank Roulund [this message]
2011-05-31 7:55 ` 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:
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='irtv22$kr$1@dough.gmane.org' \
--to=rasmus.pank@gmail.com \
--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).