Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!husc6!think!ames!amdcad!sun!pitstop!sundc!seismo!uunet!munnari!munnari.oz!kre
From: kre@munnari.oz (Robert Elz)
Newsgroups: comp.unix.wizards
Subject: Re: Re^2: Should ``csh'' be part of the System V distribution?
Message-ID: <2132@munnari.oz>
Date: 21 May 88 06:44:30 GMT
References: <2599@usceast.UUCP> <2601@usceast.UUCP> <10857@steinmetz.ge.com> <7941@brl-smoke.ARPA>
Sender: news@munnari.oz
Lines: 21

In article <7941@brl-smoke.ARPA>, gwyn@brl-smoke.ARPA (Doug Gwyn ) writes:
> In article <3141@bsu-cs.UUCP> dhesi@bsu-cs.UUCP (Rahul Dhesi) writes:
> >On 4.3BSD systems, a script that begins with "#! /bin/csh -f" will be
> 
> It most certainly does NOT work well!  In practice one ALWAYS needs
> to put the -f there,

Depends what the intended use of the script is.  If you were writing
something for just your own use, being able to write it using the same
environment that you would use to just type the commands to the shell
must surely be easier (ie: the script uses all your aliases, variables,
etc, as imported from .cshrc).

Then surely no-one sane would actually write a csh script to be used
for anything more than personal uses, its programming language is so
foul (only just a bit better than the v6 shell it replaced) that you'd
have to be insane.

So, almost no csh script should need the -f ...

kre