Commit regenerated doc/sed.texi
This commit is contained in:
1 parent
9d53087645
commit
ad0793145b
2 files changed
+7
-4
No files matched your search
@@ -2,6 +2,7 @@
|
||||
|
||||
* doc/sed-in.texi (Extended regexps): Add '|' to the list of
|
||||
differences. Note that "\|" is a GNU extension to begin with.
|
||||
* doc/sed.texi: Rebuild.
|
||||
|
||||
2010-10-20 Paolo Bonzini <bonzini@gnu.org>
|
||||
|
||||
|
||||
+6
-4
@@ -2993,10 +2993,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:
|
||||
|
||||
Reference in new issue
Block a user