Message-ID:	<001c01c232f6$625d4ae0$0100a8c0@p4>
From:	"Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
To:	<djgpp-workers AT delorie DOT com>, "Mark E." <snowball3 AT bigfoot DOT com>
References:	<3D3D61DB DOT 3206 DOT 267888 AT localhost>
Subject:	Re: Possible bash problem
Date:	Wed, 24 Jul 2002 19:41:39 +1000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000
Reply-To:	djgpp-workers AT delorie DOT com

Mark,

Any ideas on when you will have the 2.05b source available at your home
page?

I will update the Bash 2.05a at clio to 2.05b on the next update after I
download the sources. This should help out by allowing more people to try
it.

Regards,
Andrew
----- Original Message -----
From: "Mark E." <snowball3 AT softhome DOT net>
To: <djgpp-workers AT delorie DOT com>
Sent: Wednesday, July 24, 2002 4:02 AM
Subject: Re: Possible bash problem


> > The problem is that TMPDIR's "/" is turned into "\" when an external
> > program is executed.
>
> > Is that a bug? Or why is it happening?
>
> DJGPP's Bash changes '\' to '/' at startup for certain environment
variables
> (PATH, HOME, TMPDIR, and others). The opposite is usually done ('/' ->
'\')
> when creating a environment for a child program. The imported environment
is
> cached by Bash at startup, so when the value doesn't change inside Bash
then
> the imported value is exported as-is. I think the thing to do is to not
> perform the '\' to '/' magic for TMPDIR.
>
> About Bash 2.05b:
> The new Bash 2.05b has a rather large amount of changes for an a->b
upgrade,
> so I'm going to take a conservative approach and keep 2.05a available
until
> 2.05b's reliability can be determined.
>
> Mark
>
>

- Raw text -