sed-1.11 has problems with the character \377

Thread View: gnu.utils.bug

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Cliff Krumvieda Wed, 14 Oct 1992 15:20

#920

Author: Cliff Krumvieda
Date: Wed, 14 Oct 1992 15:20

32 lines
1589 bytes

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

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads