From: snowball3 AT bigfoot DOT com (Mark E.)
To: djgpp AT delorie DOT com
Subject: Re: Bash 2.03 beta update
Date: Tue, 29 Jun 1999 14:46:18 GMT
Organization: Snowball's Web
Message-ID: <3779dc0c.920896@smtp1.ibm.net>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990629170411 DOT 18841C-100000 AT is>
In-Reply-To: <Pine.SUN.3.91.990629170411.18841C-100000@is>
X-Mailer: Forte Agent 1.5/32.452
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id KAA11846
Reply-To: djgpp AT delorie DOT com

On Tue, 29 Jun 1999 17:05:27 +0300 (IDT), you wrote:

>
>On Sat, 26 Jun 1999, Mark E. wrote:
>
>> I'm also pondering making 'PATH_SEPARATOR=:' the default since 
>> Bash is a Unix shell and shell scripts expect PATH to be colon 
>> separated. Any thoughts on this?
>
>I presume this goes together with PATH_EXPAND=y, right?  If not, programs 
>that look up the PATH will be confused by the colons, since they don't 
>expect colons to be a directory separator.

When PATH_SEPARATOR is ':', the PATH variable plus a few others are always
converted to c:/foo form in the environment given to child programs.
PATH_EXPAND is for expanding paths affected by SYSROOT.

Mark

-- 
Mark E.: snowball3 AT bigfoot DOT com
http://snowball.frogspace.net/