[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

using grep with \> is not portable

From: Jim Meyering
Subject: using grep with \> is not portable
Date: Sat, 17 Mar 2007 10:16:56 +0100

One more small doc change, below.
FYI, it was prompted by the coreutils buildbot failures last night.
Fixed by today's changes to bootstrap:

-grep '^[        ]*AM_GNU_GETTEXT_VERSION\>' >/dev/null || \
+grep '^[        ]*AM_GNU_GETTEXT_VERSION(' >/dev/null || \

        * doc/autoconf.texi
        (Limitations of Usual Tools): Also list \< and \>, and mention that
        HP-UX's grep, like the one from Solaris, does not support that syntax.

Index: doc/autoconf.texi
RCS file: /sources/autoconf/autoconf/doc/autoconf.texi,v
retrieving revision 1.1136
diff -u -p -r1.1136 autoconf.texi
--- doc/autoconf.texi   17 Mar 2007 09:01:58 -0000      1.1136
+++ doc/autoconf.texi   17 Mar 2007 09:11:30 -0000
@@ -13562,8 +13562,8 @@ Portable @command{grep} regular expressi
 escape characters in the string @samp{$()address@hidden@}}.  For example,
 alternation, @samp{\|}, is common but Posix does not require its
 support in basic regular expressions, so it should be avoided in
-portable scripts.  Solaris @command{grep} does not support it.
-Similarly, @samp{\+} and @samp{\?} should be avoided.
+portable scripts.  Solaris and HP-UX @command{grep} do not support it.
+Similarly, @samp{\<}, @samp{\>}, @samp{\+} and @samp{\?} should be avoided.

 @item @command{join}

reply via email to

[Prev in Thread] Current Thread [Next in Thread]