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
Date:	Mon, 21 Aug 2000 16:02:13 -0600
Message-Id:	<200008211602.AA118293144@gammacomputer.com>
Mime-Version:	1.0
From:	"Malcolm Garland" <malcolmg AT gammacomputer DOT com>
Reply-To:	<malcolmg AT gammacomputer DOT com>
To:	<cygwin AT sourceware DOT cygnus DOT com>
Subject:	help with exporting variables
X-Mailer:	<IMail v6.00>

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?

Any help would be greatly appreciated...


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

- Raw text -