Here's how the old sed on my NeXT machine behaves:
bash-2.00$ sed 's/2/too/'
2 2 solid flesh^D
too 2 solid flesh
GNU sed 2.05 does exactly this too.
But when you go global they behave differently. My old NeXT sed:
bash-2.00$ sed -g 's/2/too/'
2 2 solid flesh^D
too too solid flesh
Here's GNU sed's variant on the above:
[root(_at_)ls550 bidmead]# sed -g 's/2/too/'
sed: illegal option -- g
Usage: sed [-nV] [--quiet] [--silent] [--version] [-e script]
[-f script-file] [--expression=script] [--file=script-file] [file...]
...in other words, collapse of stout party. Doesn't understand -g,
misinterpets it as -- g and calls it an "illegal option". Yet the GNU
man page say it does understand -g (and I should hope it would...).
Is GNU sed brain-damaged, or am I? Polite answers of all kinds
gratefully received.
el bid