Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!umd5!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.wizards
Subject: Re: Re^2: Should ``csh'' be part of the System V distribution?
Message-ID: <7941@brl-smoke.ARPA>
Date: 20 May 88 11:09:31 GMT
References: <2599@usceast.UUCP> <2601@usceast.UUCP> <10857@steinmetz.ge.com> <762@ambush.UUCP> <7924@brl-smoke.ARPA> <3141@bsu-cs.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 11

In article <3141@bsu-cs.UUCP> dhesi@bsu-cs.UUCP (Rahul Dhesi) writes:
>In article <7924@brl-smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
>writes:
>>Csh ... sources .cshrc even for scripts...
>On 4.3BSD systems, a script that begins with "#! /bin/csh -f" will be
>executed by csh without invoking .cshrc.  Note that csh was designed
>for 4.xBSD.  This mechanism works well and gives the user a choice.

It most certainly does NOT work well!  In practice one ALWAYS needs
to put the -f there, because otherwise there is absolutely no way to
control the behavior of the script.  This is similar to the standard
imported-IFS problem (fixed in BRL sh).