From: "John M. Aldrich" <fighteer AT cs DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: BASH startup
Date: Wed, 08 Jan 1997 21:10:03 -0800
Organization: Two pounds of chaos and a pinch of salt
Lines: 21
Message-ID: <32D47DAB.38B1@cs.com>
References: <5b0thq$g5e$1 AT mark DOT ucdavis DOT edu> <5b1076$nb0$1 AT mark DOT ucdavis DOT edu>
Reply-To: fighteer AT cs DOT com
NNTP-Posting-Host: ppp107.cs.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

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?

-- 
---------------------------------------------------------------------
| John M. Aldrich, aka Fighteer I |        fighteer AT cs DOT com          |
| Proud owner of what might one   |   http://www.cs.com/fighteer    |
| day be a spectacular MUD...     | Plan: To make Bill Gates suffer |
---------------------------------------------------------------------