Changed some \verb\...\ markup to the more common \code{...}. \verb\...\ is

rarely needed and should be avoided where possible since it doesn't behave
well with some processing tools (like partparse.py).

diff --git a/Doc/lib/libglob.tex b/Doc/lib/libglob.tex
index b63d153969da7c3d2797816218974a2a77819fb0..3f21b39e32a2b55c3b40741360ed761a8dc007a8 100644 (file)
--- a/Doc/lib/libglob.tex
+++ b/Doc/lib/libglob.tex
@@ -5,8 +5,8 @@
 
 The \code{glob} module finds all the pathnames matching a specified
 pattern according to the rules used by the \UNIX{} shell.  No tilde
-expansion is done, but \verb\*\, \verb\?\, and character ranges
-expressed with \verb\[]\ will be correctly matched.  This is done by
+expansion is done, but \code{*}, \code{?}, and character ranges
+expressed with \code{[]} will be correctly matched.  This is done by
 using the \code{os.listdir()} and \code{fnmatch.fnmatch()} functions
 in concert, and not by actually invoking a subshell.  (For tilde and
 shell variable expansion, use \code{os.path.expanduser(}) and

diff --git a/Doc/libglob.tex b/Doc/libglob.tex
index b63d153969da7c3d2797816218974a2a77819fb0..3f21b39e32a2b55c3b40741360ed761a8dc007a8 100644 (file)
--- a/Doc/libglob.tex
+++ b/Doc/libglob.tex
@@ -5,8 +5,8 @@
 
 The \code{glob} module finds all the pathnames matching a specified
 pattern according to the rules used by the \UNIX{} shell.  No tilde
-expansion is done, but \verb\*\, \verb\?\, and character ranges
-expressed with \verb\[]\ will be correctly matched.  This is done by
+expansion is done, but \code{*}, \code{?}, and character ranges
+expressed with \code{[]} will be correctly matched.  This is done by
 using the \code{os.listdir()} and \code{fnmatch.fnmatch()} functions
 in concert, and not by actually invoking a subshell.  (For tilde and
 shell variable expansion, use \code{os.path.expanduser(}) and