Line at a time scripts in csh

The Grey Wolf greywolf at unisoft.UUCP
Sat Jan 28 09:58:21 AEST 1989


In article <9511 at smoke.BRL.MIL> gwyn at brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
>In article <7449 at ihlpf.ATT.COM> lukas at ihlpf.UUCP (00771g-Lukas,J.) writes:
>> [ when he typed "csh foo", foo was run with sh instead ]
>
>The implementors of your csh should be congratulated for getting this
>right (for a change).  csh is supposed to feed scripts to a Bourne shell.

Where are you getting your documentation, Doug?  Since when, if you type

% csh foo

does it feed "foo" to the Bourne shell?  This is not correct, and certainly
not normal!  If I feed a script to csh, csh had better run it, since that
was my intention.  Otherwise, it would be rather redundant, what?

>The only exception would be if your kernel doesn't support #! execs but
>(ALL) your shells are expected to take care of this, in which case the
>#! line should be interpreted and the appropriate processor run to handle
>the script.

System V, release 3 does not support #! execs.  I know, because I *work*
with them all bloody day.  #! is constantly ignored.

---
Roan Anderson, Software Engineer, UniSoft Corp.
6121 Hollis St. Emeryville, CA  94608
My opinions are my own and not those of UniSoft Corporation.
If I want your opinion, I'll give it to you.
-- 
...TheysaidDoyouseethebiggreenglowinthedarkhouseuponthehill?andIsaidYesIseethebiggreenglowinthedarkhouseuponthehillTheresabigdarkforestbetweenmeandthebiggreenglowinthedarkhouseuponthehillandalittleoldladyonaHoovervacuumcleanersayingIllgetyoumyprettyandyourlittledogTototoo
I don't even *HAVE* a dog Toto...



More information about the Comp.unix.questions mailing list