Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!gem.mps.ohio-state.edu!ginosko!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.unix.questions
Subject: Re: csh setenv problem
Message-ID: <2375@auspex.auspex.com>
Date: 21 Aug 89 18:06:56 GMT
References: <SAAF.89Aug16153940@joker.optics.rochester.edu> <2312@zaphod.axion.bt.co.uk>
Reply-To: guy@auspex.auspex.com (Guy Harris)
Organization: Auspex Systems, Santa Clara
Lines: 10

>	The Bourne Shell (sh) has an export command, which exports
>a variable to the parent shell.

Wrongo.  The Bourne shell has an "export" command, which causes a shell
variable to be exported to *CHILD* shells.  It does *NOT* "export"
variables to the parent shell; a process can't just "export" an environment to
an already-existing process, it have to politely ask said process to
import said variable, using some protocol it and said process have
agreed on.  There is no "standard" protocol of that sort already
implemented by any shell I know of.