Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <fdb072ec0407210702185912ce@mail.gmail.com>
Date: Wed, 21 Jul 2004 10:02:06 -0400
From: Robert Pendell <shinji257 AT gmail DOT com>
To: Cygwin eMail List <cygwin AT cygwin DOT com>
Subject: Re: setting windows environment variables
In-Reply-To: <D7FBE8A336018A4EB5EBDC6C898821930991C78A@HUELVA.belgium.fhm.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <D7FBE8A336018A4EB5EBDC6C898821930991C78A AT HUELVA DOT belgium DOT fhm DOT de>
X-IsSubscribed: yes

And it is compatible for use on *bsd, linux, and unix.  So if you are
writing a script to be used on a real *nix or *bsd system then that
would be the one to use.

On Wed, 21 Jul 2004 15:00:26 +0200, Morche Matthias wrote:
> ...to set environmental variables for windows you can use regtool...
> But in that case they get persistent...
> 
> ...and the simplest equivalent to start is using & to background the command...
> 
>   matthias
> 
> 
> 
> > -----Original Message-----
> > From: cygwin-owner AT cygwin DOT com
> > [mailto:cygwin-owner AT cygwin DOT com]On Behalf
> > Of Larry Hall
> > Sent: Tuesday, July 20, 2004 10:38 PM
> > To: Jason Joines; cygwin AT cygwin DOT com
> > Subject: Re: setting windows environment variables
> >
> >
> > At 04:18 PM 7/20/2004, you wrote:
> > >    I have a Cygwin BASH script which takes user input, uses
> > ldapsearch, etc., to set a bunch of environment variables.  I
> > can then use these from bash with no problem.  I would also
> > like to make these environment variables available to the
> > windows command interpreter.
> > >    Is there anyway to do this?
> >
> >
> > Only if the windows command interpreter is a child of the
> > bash process you
> > run from.  Otherwise, your best bet is to export the variables as some
> > batch file and run that in the windows command interpreter.
> >
> >
> > >    Also, is there a BASH equivalent of the windows cmd
> > start command that lets you start many processes without
> > having to wait on each to finish?
> >
> >
> > How about 'cygstart'?
> >
> >
> > --
> > Larry Hall                              http://www.rfk.com
> > RFK Partners, Inc.                      (508) 893-9779 - RFK Office
> > 838 Washington Street                   (508) 893-9889 - FAX
> > Holliston, MA 01746
> >
> >
> > --
> > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > Problem reports:       http://cygwin.com/problems.html
> > Documentation:         http://cygwin.com/docs.html
> > FAQ:                   http://cygwin.com/faq/
> >
> >
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 
> 


-- 
Robert Pendell
shinji257 AT gmail DOT com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/