AMK's megapatch:
* \bcode, \ecode added everywhere
* \label{module-foo} added everywhere
* A few \seealso sections added.
* Indentation fixed inside verbatim in lib*tex files
diff --git a/Doc/libpdb.tex b/Doc/libpdb.tex
index 84ae332..9785a40 100644
--- a/Doc/libpdb.tex
+++ b/Doc/libpdb.tex
@@ -29,7 +29,7 @@
The debugger's prompt is ``\code{(Pdb) }''.
Typical usage to run a program under control of the debugger is:
-\begin{verbatim}
+\bcode\begin{verbatim}
>>> import pdb
>>> import mymodule
>>> pdb.run('mymodule.test()')
@@ -40,15 +40,15 @@
NameError: 'spam'
> <string>(1)?()
(Pdb)
-\end{verbatim}
-
+\end{verbatim}\ecode
+%
\code{pdb.py} can also be invoked as
a script to debug other scripts. For example:
\code{python /usr/local/lib/python1.4/pdb.py myscript.py}
Typical usage to inspect a crashed program is:
-\begin{verbatim}
+\bcode\begin{verbatim}
>>> import pdb
>>> import mymodule
>>> mymodule.test()
@@ -63,8 +63,8 @@
> ./mymodule.py(3)test2()
-> print spam
(Pdb)
-\end{verbatim}
-
+\end{verbatim}\ecode
+%
The module defines the following functions; each enters the debugger
in a slightly different way:
@@ -224,11 +224,11 @@
of the statement resembles a debugger command.
To set a global variable, you can prefix the assignment
command with a ``\code{global}'' command on the same line, e.g.:
-\begin{verbatim}
+\bcode\begin{verbatim}
(Pdb) global list_options; list_options = ['-l']
(Pdb)
-\end{verbatim}
-
+\end{verbatim}\ecode
+%
\item[q(uit)]
Quit from the debugger.