From: "Weiqi Gao" <weiqigao AT crl DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: BASH startup
Date: 9 Jan 1997 12:44:07 GMT
Organization: CRL Dialup Internet Access
Lines: 25
Message-ID: <01bbfe2a$d10ea4e0$0f02000a@weiqigao>
References: <5b0thq$g5e$1 AT mark DOT ucdavis DOT edu> <5b1076$nb0$1 AT mark DOT ucdavis DOT edu> <32D47DAB DOT 38B1 AT cs DOT com>
NNTP-Posting-Host: crl7.crl.com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

John M. Aldrich <fighteer AT cs DOT com> wrote in article
<32D47DAB DOT 38B1 AT cs DOT com>...
> Jeffrey Taylor wrote:
> > 
> > I found part of the problem, I was using "set LFN=n" instead of
"LFN=n".
> > I expected set with no arguments to show these variable values, but it
> > doesn't.  However, "echo $LFN" does show the value I expect.  Another
> > example, I did:
> > 
> > PS1=$HISTCMD\$
> > PS1=bash\$
> > DJGPP=c:/djgpp_v2.01/djgpp.env
> 
> I don't know enough about bash to be sure, but I know that in ksh you
> have to explicitly 'export' variables before they become part of the
> shell environment.  Does bash have a similar requirement?

Yes.  The current shell gets the variable whether you export or not. 
Subshells gets the variable only after you export it.  Is that how it works
in ksh?

-- 
Weiqi Gao
weiqigao AT crl DOT com