On Sat, 1 Jul 2000, David W. Tamkin wrote:
S> Gotta be careful there ... some versions of sed don't let you put the -n
S> and the -e in the same argument like that.
OK; I've never run into that. That is a big deficiency, because if they
can't handle -n and -e in one argument, how can they deal with hash-bang
sedfiles that start
#!/usr/bin/sed -nf
Hmm, I'm not sure. I only know about the problem because somebody on the
zsh-workers mailing list reported that one of the zsh build utilities was
failing because "sed -ne something -e otherthing" reported "-e: file not
found". This was on some flavor of IRIX.
So perhaps that sed accepts either a single cluster of options or a series
of separate options, but not a mixture of the two.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail