Date: Wed, 5 Apr 2000 11:36:30 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT bigfoot DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Bash 2.04 beta 1 now available
In-Reply-To: <38E9E844.8417.11C6D0@localhost>
Message-ID: <Pine.SUN.3.91.1000405113613.20661I-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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
Precedence: bulk


On Tue, 4 Apr 2000, Mark E. wrote:

> The transforming of the PATH env. variable still works when 
> 'PATH_SEPARATOR=:'. That isn't affected by PATH_EXPAND anyway.

Sorry, I thought PATH_EXPAND was affecting that as well.

> The part that 
> was removed is the ugly code that detects and fixes up 'prog.exe 
> /dev/c/djgpp/bin' to 'prog.exe c:/djgpp/bin'. This is the part that has to be 
> redone. Bash does use a function to return an argv[] array based on Bash's 
> internal argument list, but I haven't looked yet to see if it can be used.

Well, I think it might be a good idea to retain this feature.  I'd
suggest to see if the function you mentioned could be used for this
purpose.