Message-Id: <1.5.4.16.19970109161927.34cf0bea@pop.verisim.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 09 Jan 1997 11:19:27 -0500
To: djgpp AT delorie DOT com
From: Takashi Toyooka <ttoyooka AT verisim DOT com>
Subject: Re: BASH startup

At 21:10 1997/01/08 -0800, you wrote:
>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.
>
>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.  You can also use 'declare -x' which, AFAIK, is equivalent.

On a related topic, does anyone know how to increase the size of the
environment under bash?  I was trying to use it as my default shell
(declaring SHELL=C:\...\BASH.EXE in CONFIG.SYS), but it runs out of
environment space when I try to declare all the variables I need.

Has anyone else gotten bash to work as their default shell?

Thanks,
Takashi