From: Akim Demaille Date: Thu, 25 Apr 2002 09:14:39 +0000 (+0000) Subject: * doc/autoconf.texi (Limitations of Usual Tools): sed and `!'. X-Git-Tag: AUTOCONF-2.53b~99 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=21011a0300a528bb3ee4b099d1854da4b7a1d1a1;p=thirdparty%2Fautoconf.git * doc/autoconf.texi (Limitations of Usual Tools): sed and `!'. Thanks to Paul Eggert. --- diff --git a/ChangeLog b/ChangeLog index 3c38e99e4..0aacf5087 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2002-04-25 Akim Demaille + + * doc/autoconf.texi (Limitations of Usual Tools): sed and `!'. + Thanks to Paul Eggert. + 2002-04-25 Akim Demaille * lib/autoconf/general.m4 (_AC_INIT_DEFAULTS): Let ac_subst_files diff --git a/doc/autoconf.texi b/doc/autoconf.texi index 0ed6ad184..d0ab36ac4 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi @@ -9885,6 +9885,18 @@ matched''. All descendants of Bell Lab's V7 @command{sed} (at least; we don't have first hand experience with older @command{sed}s) have supported it. +@sc{posix} requires that you must not have any white space between +@samp{!} and the following command. It is OK to have blanks between +the address and the @samp{!}. For instance, on Solaris 8: + +@example +$ @kbd{echo "foo" | sed -n '/bar/ ! p'} +@error{}Unrecognized command: /bar/ ! p +$ @kbd{echo "foo" | sed -n '/bar/! p'} +@error{}Unrecognized command: /bar/! p +$ @kbd{echo "foo" | sed -n '/bar/ !p'} +foo +@end example @item @command{sed} (@samp{t}) @c ---------------------------