Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbosgd!gatech!seismo!elsie!ado
From: ado@elsie.UUCP (Arthur David Olson)
Newsgroups: net.bugs.4bsd
Subject: 4.[123]bsd csh script handling bug--who's got the "right" fix?
Message-ID: <6042@elsie.UUCP>
Date: Mon, 24-Mar-86 16:53:46 EST
Article-I.D.: elsie.6042
Posted: Mon Mar 24 16:53:46 1986
Date-Received: Wed, 26-Mar-86 03:37:25 EST
Organization: NIH-LEC, Bethesda, MD
Lines: 25
Keywords: bsd csh

If you
    repeat 25 echo oops 6789012345678901234567890123456789012345678901 >> file
and then either
    csh file
or
    cat file | csh
you get this output:
    oops: Command not found.
    789012345678901: Command not found.
where "780912345678901" turns out to be what's stored in "file" starting at the
1025th byte.  Could be disastrous if you had something such as
    reform -r *
starting at the 1021st byte--this would end up doing the dreaded
    rm -r *

Now let's set aside the question of whether you really "ought to" use "sh"
rather than "csh" for scripts.  I myself use "sh."  However, there are users
who want to create "csh" scripts.  And so the question:  what's the best way
to fix the above bug and prevent possible calamity for such users?
--
Bugs is a Warner Brothers trademark.
Bug is a Volkswagen trademark.
--
	UUCP: ..decvax!seismo!elsie!ado		ARPA: elsie!ado@seismo.ARPA
	DEC, VAX, Elsie & Ado are Digital, Borden & Shakespeare trademarks.