Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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:	<3E551EB0.5040004@newsguy.com>
Date:	Thu, 20 Feb 2003 12:30:08 -0600
From:	David Bath <davidbath AT newsguy DOT com>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language:	en-us, en
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Question re. export environment variable

> Date: Thu, 20 Feb 2003 12:38:43 -0500
> From: Shing-Fat Fred Ma <fma AT doe DOT carleton DOT ca>
> To: Bob McGowan <rmcgowan AT veritas DOT com>
> CC: cygwin AT cygwin DOT com
> Subject: Re: Question re. export environment variable
> 
> Thanks, Bob.  That's the way I expected it to work.
> I was just unsure of whether there was something
> cygwin-specific, as it seems strange that something
> like HOSTNAME is not marked for export at the time
> that it is set.  I'll stick it into ~/.bashrc.
> 
> Fred

I've always used the "set -a" shell builtin command in my .bashrc or 
.kshrc files which then exports all environment variables to all spawned 
bshells.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -