summaryrefslogtreecommitdiff
path: root/doc/sed-in.texi
diff options
context:
space:
mode:
authorPaolo Bonzini <bonzini@gnu.org>2010-10-31 22:56:15 +0100
committerPaolo Bonzini <bonzini@gnu.org>2010-10-31 22:56:15 +0100
commit8eee8cbf0e93d8b3695225dc1db0b8ea27c6cf11 (patch)
tree55a33cfd8e08d49fcf640d8e319083668a16eb73 /doc/sed-in.texi
parentdeb6f38c216948fcdd5d910a1dc30e830251eaf0 (diff)
downloadsed-8eee8cbf0e93d8b3695225dc1db0b8ea27c6cf11.tar.gz
2010-10-31 Gerald Pfeifer <gerald@pfeifer.com>
* doc/sed-in.texi (Extended regexps): Add '|' to the list of differences. Note that "\|" is a GNU extension to begin with.
Diffstat (limited to 'doc/sed-in.texi')
-rw-r--r--doc/sed-in.texi10
1 files changed, 6 insertions, 4 deletions
diff --git a/doc/sed-in.texi b/doc/sed-in.texi
index 00874ba..494e832 100644
--- a/doc/sed-in.texi
+++ b/doc/sed-in.texi
@@ -2824,10 +2824,12 @@ the @env{LC_COLLATE} and @env{LC_CTYPE} environment variables to @samp{C}.
The only difference between basic and extended regular expressions is in
the behavior of a few characters: @samp{?}, @samp{+}, parentheses,
-and braces (@samp{@{@}}). While basic regular expressions require
-these to be escaped if you want them to behave as special characters,
-when using extended regular expressions you must escape them if
-you want them @emph{to match a literal character}.
+braces (@samp{@{@}}), and @samp{|}. While basic regular expressions
+require these to be escaped if you want them to behave as special
+characters, when using extended regular expressions you must escape
+them if you want them @emph{to match a literal character}. @samp{|}
+is special here because @samp{\|} is a GNU extension -- standard
+basic regular expressions do not provide its functionality.
@noindent
Examples: