Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.unix.questions
Subject: Re: Line at a time scripts in csh
Message-ID: <9537@smoke.BRL.MIL>
Date: 28 Jan 89 07:01:42 GMT
References: <4116@paris.ics.uci.edu> <909@ubu.warwick.UUCP> <7296@ihlpf.ATT.COM> <872@auspex.UUCP> <7372@ihlpf.ATT.COM> <891@auspex.UUCP> <7449@ihlpf.ATT.COM> <9511@smoke.BRL.MIL> <1837@unisoft.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 11

In article <1837@unisoft.UUCP> greywolf@unisoft.UUCP (The Grey Wolf) writes:
>In article <9511@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
>>In article <7449@ihlpf.ATT.COM> lukas@ihlpf.UUCP (00771g-Lukas,J.) writes:
>>> [ when he typed "csh foo", foo was run with sh instead ]

No, that wasn't what he said!  He was running interactively under csh,
and typing "foo" invoked an "sh" to interpret it.

>System V, release 3 does not support #! execs.

I never said it did.