[Coco] Re: CHX broke? for 6309l2v030201

[Charlie]

This sounds exactly like the "problem" I posted that started this whole  
thread. :-)

Charlie

On Wed, 14 Jul 2004 11:26:39 -0400, Coco Pilot  
<cocopilot at verizon.net> wrote:

> Paul T. Barton wrote:
>
>> Versions:
>> 6309-L2-V030201
>> and the previous one too;
>>
>> Inside of a Ramdisk setup script I have:
>> (at the end)
>>
>> blahblahblah
>> CHX /R0/CMDS
>>
>> It never changes. When the script is done,
>> typing "PXD" gives me /DD/CMDS instead of
>> /R0/CMDS.
>>
>> What gives with this?
>> No more CHX inside of a script?
>>
>> ---
>>
>> It works if I type CHX /R0/CMDS manually.
>>
> This reminds me very much of the way UNIX shells work.  Changes to the  
> environment inside
> a script are only valid for the duration of the script.  In UNIX, to  
> make these permanent, you
> would need to 'source'  the scripts in order to make the changes in the  
> calling shell's environment.
>
> Does Shell2.2a allow this? -Ben
>



-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/