Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frame with both optional and overlay specification can give frame-break #743

Open
blefloch opened this issue Dec 6, 2021 · 4 comments
Open
Labels
bug Something isn't working

Comments

@blefloch
Copy link

blefloch commented Dec 6, 2021

A frame can have both an overlay specification in angle brackets and an optional argument. In that order, it works (see frame-A below). But in the other order, one gets <1> typeset, with < alone on one frame, and 1> on the next one, which is pretty puzzling.

\documentclass{beamer}
\begin{document}
\begin{frame}<1>[label=frame-A]
\end{frame}
\begin{frame}[label=frame-B]<1>
\end{frame}
\end{document}
@samcarter
Copy link
Collaborator

samcarter commented Dec 7, 2021

Only the first version is valid syntax, the frame environment is documented like this:

\begin{frame}<⟨overlay specification⟩>[<⟨default overlay specification⟩>][⟨options⟩]{⟨title⟩}{⟨subtitle⟩} 
⟨environment contents⟩
\end{frame}

@blefloch
Copy link
Author

blefloch commented Dec 7, 2021

Thanks. Nevertheless the second one should not give two frames but a single frame with <1> being typeset.

@samcarter
Copy link
Collaborator

samcarter commented Dec 7, 2021

Even in the middle of a frame, a <1> won't be typeset as "<1>" (at least not without additional tricks)
document

@blefloch
Copy link
Author

blefloch commented Dec 7, 2021

Correct, I should have added \usepackage[T1]{fontenc} to preempt this point. My surprise is with the fact that there is a frame break: < (or rather ¡) gets on one page and 1> (or rather 1¿) on the next.

@samcarter samcarter added the bug Something isn't working label Dec 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants