Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<39A1DDFE.71D6CA17@veritas.com>
Date:	Mon, 21 Aug 2000 18:57:18 -0700
From:	Bob McGowan <rmcgowan AT veritas DOT com>
Organization:	VERITAS Software
X-Mailer:	Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	malcolmg AT gammacomputer DOT com
CC:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: help with exporting variables
References:	<200008211602 DOT AA118293144 AT gammacomputer DOT com>

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"

You may want to pose this question to one of the bash related news
groups, too.

-- 
Bob McGowan
Staff Software Quality Engineer
VERITAS Software
rmcgowan AT veritas DOT com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -