Alex Hornung (via DragonFly issue tracker) wrote:
> Alex Hornung <ahornung@gmail.com> added the comment:
>
> Standard[1] dictates: "Whenever the pattern space is written to standard
> output or a named file, sed shall immediately follow it with a <newline>."
>
> In my personal opinion, though, I'd prefer to see a gnu-compatible sed, even
> if that means breaking standards compliance.
The standard is exceptionally clear on this, and I don't quite see why we should introduce a regression for an insignificant script which assumes sed is operating in a non-conforming way. Their shell script is wrong.
cheers
simon