Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!mcsun!ukc!dcl-cs!gdt!gdr!exspes
From: exspes@gdr.bath.ac.uk (P E Smee)
Newsgroups: comp.unix.questions
Subject: Re: export vars from cshell script?
Message-ID: <1989Nov16.110837.10315@gdt.bath.ac.uk>
Date: 16 Nov 89 11:08:37 GMT
References: <1815@gazette.bcm.tmc.edu> <869@awdprime.UUCP>
Reply-To: exspes@gdr.bath.ac.uk (P E Smee)
Organization: University of Bristol c/o University of Bath
Lines: 21

In article <869@awdprime.UUCP> @cs.utexas.edu:ibmaus!auschs!woan.austin.ibm.com!ron writes:
>In article <1815@gazette.bcm.tmc.edu>, heidi@kiwi.bcm.tmc.edu (Heidi 
>writes:
>> Is there an equivalent in the Cshell to the Bourne shell's export
>> facility?  We have would like to define new environment variables in a
>> shell, and have them be known to subsequent processes.
>
>I may be way off base, but I have always been under the impression that
>setenv automatically exported them??!!

Sposed to do, yep.  Problem is that people who are just moving to csh
from sh tend to overlook 'setenv', because csh also has 'set' which
looks at first glance like it ought to be equivalent to sh 'set'.
(In fact, I suppose it is.  It's the fact that csh lacks 'export' which
is critical, and which is what they notice.)

-- 
 Paul Smee               |    JANET: Smee@uk.ac.bristol
 Computer Centre         |   BITNET: Smee%uk.ac.bristol@ukacrl.bitnet
 University of Bristol   | Internet: Smee%uk.ac.bristol@nsfnet-relay.ac.uk
 (Phone: +44 272 303132) |     UUCP: ...!uunet!ukc!gdr.bath.ac.uk!exspes