From:	"Mark E." <snowball3 AT softhome DOT net>
To:	djgpp-workers AT delorie DOT com
Date:	Tue, 23 Jul 2002 14:02:03 -0400
MIME-Version:	1.0
Subject:	Re: Possible bash problem
Message-ID:	<3D3D61DB.3206.267888@localhost>
In-reply-to:	<200207132039.g6DKdYf05422@speedy.ludd.luth.se>
X-mailer:	Pegasus Mail for Windows (v4.01)
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> 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 -