From: yaxp <yaxp@cock.li>
To: emacs-orgmode@gnu.org
Subject: org-beamer: Insert \framebreak between blocks
Date: Wed, 25 Oct 2023 00:24:19 +0530 [thread overview]
Message-ID: <0e156422-6ac3-4104-91c9-87507f14de12@cock.li> (raw)
Adding a framebreak between blocks does not work.
```
#+latex_class: beamer
#+options: H:1
# [snip]
* Example :B_frame:
:PROPERTIES:
:BEAMER_opt: allowframebreaks
:BEAMER_env: frame
:END:
** This should be on frame 1
- Some text
#+LATEX: \framebreak
** This should be on frame 2
- Some text
```
Exporting this to PDF and examining the resulting file reveals that the
\framebreak is inserted before the \end{block}.
```
% [snip]
\begin{frame}[allowframebreaks]{Example}
\begin{block}{This should be on frame 1}
\begin{itemize}
\item Some text
\framebreak % This is the offending line
\end{itemize}
\end{block}
\begin{block}{This should be on frame 2}
\begin{itemize}
\item Some text
\end{itemize}
\end{block}
\end{frame}
% [snip]
```
How do I not have this?I want the two blocks to be on different frames.
Manually fixing the .tex file fixes the issue but I don't want to do
that for large files.
Fixed .tex file included for completion:
```
% [snip]
\begin{block}{This should be on frame 1}
\begin{itemize}
\item Some text
% ^1
\end{itemize}
\end{block}
\framebreak % Moved this line from ^1.
\begin{block}{This should be on frame 2}
\begin{itemize}
\item Some text
\end{itemize}
\end{block}
% [snip]
```
--
(yaxp me) => t
next reply other threads:[~2023-10-24 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 18:54 yaxp [this message]
2023-10-25 9:00 ` org-beamer: Insert \framebreak between blocks Fraga, Eric
2023-10-25 16:02 ` yaxp
2023-10-25 16:27 ` Fraga, Eric
2023-10-25 16:32 ` yaxp
2023-10-25 16:44 ` yaxp
2023-10-25 16:13 ` yaxp
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=0e156422-6ac3-4104-91c9-87507f14de12@cock.li \
--to=yaxp@cock.li \
--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).