diff options
| author | Paolo Bonzini <bonzini@gnu.org> | 2010-11-01 15:33:53 +0100 |
|---|---|---|
| committer | Paolo Bonzini <bonzini@gnu.org> | 2010-11-01 15:33:53 +0100 |
| commit | 699fd06fadcf65c22aef350f9865e3815cc49432 (patch) | |
| tree | 72533b2cb9f92d829b32714e24f4c1c5c3613e9f | |
| parent | 971249a0206e8e2cde0e8fb301434886a88c6259 (diff) | |
| download | sed-699fd06fadcf65c22aef350f9865e3815cc49432.tar.gz | |
Commit regenerated doc/sed.texi
| -rw-r--r-- | ChangeLog | 1 | ||||
| -rw-r--r-- | doc/sed.texi | 10 |
2 files changed, 7 insertions, 4 deletions
@@ -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> diff --git a/doc/sed.texi b/doc/sed.texi index 528573f..f04da80 100644 --- a/doc/sed.texi +++ b/doc/sed.texi @@ -2991,10 +2991,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: |