buggy sed on Darwin?

2005-12-11 Thread Werner LEMBERG
[I'm writing this here so that the information can be included into autoconf.info in case it is really a bug.] Consider this pipeline makeinfo --version | sed 's/^.* \([^ ]\+\)$/\1/;1q' with GNU sed 4.0.9 I get 4.8 but with the (BSD) sed from OS X I get makeinfo (GNU texinfo) 4.8 I wo

Re: buggy sed on Darwin?

2006-03-12 Thread Noah Misch
On Sun, Dec 11, 2005 at 12:34:42PM +0100, Werner LEMBERG wrote: > Consider this pipeline > > makeinfo --version | sed 's/^.* \([^ ]\+\)$/\1/;1q' > > with GNU sed 4.0.9 I get > > 4.8 > > but with the (BSD) sed from OS X I get > > makeinfo (GNU texinfo) 4.8 > > I wonder whether this is a

Re: buggy sed on Darwin?

2006-03-12 Thread Werner LEMBERG
> > I wonder whether this is a BSD sed bug or whether I'm doing > > something wrong. > > GNU sed recognizes `\+' as shorthand for `\{1,\}', but POSIX leaves > its meaning undefined. I suspect BSD sed treats it like literal > `+'. Other people already pointed that out to me. Thanks for your answ