summaryrefslogtreecommitdiffstats
path: root/Doc/libregex.tex
diff options
context:
space:
mode:
authorGuido van Rossum <guido@python.org>1997-12-30 20:38:16 (GMT)
committerGuido van Rossum <guido@python.org>1997-12-30 20:38:16 (GMT)
commiteb0f066fb84e71f418cf6a27c38b128aee33a834 (patch)
treeb2695f000fd9119a7eabe7d7beff8c413ddcf097 /Doc/libregex.tex
parent51ca6e3e42d6ad733dae25c7db7c89415e7cf962 (diff)
downloadcpython-eb0f066fb84e71f418cf6a27c38b128aee33a834.zip
cpython-eb0f066fb84e71f418cf6a27c38b128aee33a834.tar.gz
cpython-eb0f066fb84e71f418cf6a27c38b128aee33a834.tar.bz2
Correct small nits reported by Rob Hooft.
Diffstat (limited to 'Doc/libregex.tex')
-rw-r--r--Doc/libregex.tex4
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/libregex.tex b/Doc/libregex.tex
index cea8d64..2f8fbd8 100644
--- a/Doc/libregex.tex
+++ b/Doc/libregex.tex
@@ -37,7 +37,7 @@ regular expression represented as a string literal, you have to
\emph{quadruple} it or enclose it in a singleton character class.
E.g.\ to extract \LaTeX\ \samp{\e section\{{\rm
\ldots}\}} headers from a document, you can use this pattern:
-\code{'[\e ] section\{\e (.*\e )\}'}. \emph{Another exception:}
+\code{'[\e ]section\{\e (.*\e )\}'}. \emph{Another exception:}
the escape sequece \samp{\e b} is significant in string literals
(where it means the ASCII bell character) as well as in Emacs regular
expressions (where it stands for a word boundary), so in order to
@@ -125,7 +125,7 @@ The special sequences consist of '\code{\e}' and a character
from the list below. If the ordinary character is not on the list,
then the resulting RE will match the second character. For example,
\code{\e\$} matches the character '\$'. Ones where the backslash
-should be doubled are indicated.
+should be doubled in string literals are indicated.
\begin{itemize}
\item[\code{\e|}]\code{A\e|B}, where A and B can be arbitrary REs,