I thought there was no restriction of what could be between
a \begin{verbatim} and
\end{verbatim}
in LaTeX.
I get the following transcript however if I include
the output from `cat /usr/include/*.h` on hpux in a simple
document for testing the verbatim environment.
Document source :
--starts here--
\documentclass{article}
\begin{document}
\begin{verbatim}
`cat /usr/include/*.h` % text directly included not via file commands !
\end{verbatim}
\end{document}
% latex source.tex
This is TeX, Version 3.1415 (C version 6.1)
(test.tex
LaTeX2e <1994/12/01>
Hyphenation patterns for english, dutch, german, french, loaded.
(/imec/software/tex/lib/texmf/tex/latex2e/base/article.cls
Document Class: article 1994/12/09 v1.2x Standard LaTeX document class
(/imec/software/tex/lib/texmf/tex/latex2e/base/size10.clo)) (test.aux)
Runaway argument?
^^M^^M/* @(#) $Revision: 64.1 $ */^^M/*^^M * Format of an a.out heade\ETC.
! Forbidden control sequence found while scanning use of \@xverbatim.
<inserted text>
\par
l.6126 ^^L
?
Can someone explain?
I am very confused since I get no errors if I only include
the first 10 lines of the `cat ....` which then STILL includes
the lines where the original error is generated !
Thanks for your help ,
--
Marc (el...@imec.be)
'Waterdust is fine but even hydrogen would have lead
to a never ending story...'
This is supposed to be the case.
> I get the following transcript however if I include
> the output from `cat /usr/include/*.h` on hpux in a simple
> document for testing the verbatim environment.
>[...]
>Runaway argument?
>^^M^^M/* @(#) $Revision: 64.1 $ */^^M/*^^M * Format of an a.out heade\ETC.
>! Forbidden control sequence found while scanning use of \@xverbatim.
><inserted text>
> \par
>l.6126 ^^L
>
>?
>
> Can someone explain?
It's a bug. <control>L (form feed in ISO 646) is active and
\outer\def'd to \par in LaTeX. Apparently, the innoculation of dodgy
characters for \verbatim doesn't affect <control>L. If you're using
LaTeX2e, report the bug (quoting me as the authority declaring it _is_
a bug, if you like). You may get told that what's needed is a
documentation upgrade; you would get a downwards pointing arrow in
place of your <control>L if the bug wasn't there...
--
Robin (Campaign for Real Radio 3) Fairbairns r...@cl.cam.ac.uk
U of Cambridge Computer Lab, Pembroke St, Cambridge CB2 3QG, UK
Private page: http://www.cl.cam.ac.uk/users/rf/robin.html