# \pause won't generate extra slides in a containsverbatim frame

It seems that the [containsverbatim] option when applied to a frame prevents beamer from generating intermediate slides if text animation is wanted in it. Only the first step of the animation is printed as a result.

Sample code:

\documentclass{beamer}
\begin{document}
\begin{frame}[containsverbatim]
\frametitle{Tests anim}
blah
\pause
blah²
\end{frame}
\end{document}

My question then comes in two parts:

1. Is this a bug or did I miss something?
2. If it's a bug, is there a workaround?
-
I have the feeling that containsverbatim is an old option that is now deprecated (it doesn't appear in the manual); probably it's [fragile] that you need. –  egreg May 13 '12 at 19:16
I feel really stupid right now but I'm not sure I found the correct, up to date documentation. I'd really appreciate a pointer towards the manual you use, just to be sure I'm working on an healthy basis. Sorry to have to ask that :( –  Mog May 13 '12 at 19:28
If you have a Unix system, then the shell command texdoc beamer will present you the manual; see texdoc.net/texmf-dist/doc/latex/beamer/doc/beameruserguide.pdf for an online version. –  egreg May 13 '12 at 19:37
Thanks for the pointers :) –  Mog May 13 '12 at 19:38

The common approach to typeset frames with verbatim content is the fragile option, which works well with overlays:

\documentclass{beamer}
\begin{document}

\begin{frame}[fragile]
\frametitle{Tests anim}
blah
\pause
blah
\end{frame}

\end{document}

I hardly remember the containsverbatim option and my beamer manual (v3.10) does not mention it. The only reference I found for it is in the ChangeLog of the beamer class:

2004-02-18 Till Tantau , Version 2.00

- Added a containsverbatim option to the \frame command. Should be
used instead of the old \frame<all:1> (which is, however, still
supported).

So the observed effect is not a bug, but a feature :-), as \frame<all:1> is the syntax in beamer to suppress all, but the first slide from a frame. The option name containsverbatim seams to be pretty misleading; however, given how beamers overlay mechanism works (by scanning the frame content multiple times, which does not work well together with verbatim environments), I guess it was just the way to typeset verbatim contents.

Later, Till added the more powerful fragile option:

2004-10-11 Till Tantau

Version 3.01: