🚀 go-pugleaf

Howdy:

GNU sed-1.11 isn't behaving like Sun sed (which, admittedly, may or
may not be wrong).  We're running sed on sparcstations under SunOS
4.1.1.

Consider the following two scripts, called "sedtest" and "sedtestgnu":
======================================================================
#! /bin/csh -f
/bin/sed -e "s/\377/newtext/g"
======================================================================
#! /bin/csh -f
/usr/local/gnu/bin/sed -e "s/\377/newtext/g"
======================================================================

The "\377" above isn't the four characters "\377"; it's what emacs
types when you enter "C-q 377".  Also, we keep sed-1.11 in
/usr/local/gnu/bin/sed.

Now:
======================================================================
[~] leo% echo abc | sedtest
abc
[~] leo% echo abc | sedtestgnu
/usr/local/gnu/bin/sed: Unexpected End-of-file
[~] leo%
======================================================================

It looks like sed-1.11 thinks that \377 is an EOF marker, which is
both wrong and inconvenient.  Is this a fixable bug?

						--Cliff Krumvieda