Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <39A1DDFE.71D6CA17@veritas.com> Date: Mon, 21 Aug 2000 18:57:18 -0700 From: Bob McGowan Organization: VERITAS Software X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: malcolmg@gammacomputer.com CC: cygwin@sourceware.cygnus.com Subject: Re: help with exporting variables References: <200008211602.AA118293144@gammacomputer.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit 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@veritas.com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com