Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <20000822123441.10654.qmail@web125.yahoomail.com> Date: Tue, 22 Aug 2000 05:34:41 -0700 (PDT) From: Earnie Boyd Subject: Re: help with exporting variables To: Bob McGowan , malcolmg AT gammacomputer DOT com Cc: cygwin AT sourceware DOT cygnus DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- Bob McGowan wrote: > Malcolm Garland wrote: > > > > Hi, > > I'm Malcolm. I've created a series of bourne shell scripts which set a > series of environment > variables. Using bash, we are attempting to > export/use these scripts on NT. When we run a > single line: "bash > 'script-name', the variables are set locally, but the NT "global" environment > > variables are not modified. When execute the exact scripts, AFTER entering > the bash environment > (i.e., level with the bash prompt versus the DOS > prompt) the environment variables are set > globally. How can we alter the > NT global environment variables using a single line command > directive such > as, > > $ bash "script-name" Options? > > Maybe? > > bash -c "source script-name" > NO!! It is impossible to do what Malcolm wants the way he wants to do it. It is the nature of the way parent/child processes work. The child can inherit from the parent; but, the parent can't inherit from the child. Cheers, ===== --- Earnie Boyd: __Cygwin: POSIX on Windows__ Cygwin Newbies: __Minimalist GNU for Windows__ Mingw32 List: Mingw Home: __________________________________________________ Do You Yahoo!? Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/ -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com