Date: Tue, 29 Jun 1999 18:13:51 +0300 (IDT)
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 AT delorie DOT com
Subject: Re: Bash 2.03 beta update
In-Reply-To: <3779dc0c.920896@smtp1.ibm.net>
Message-ID: <Pine.SUN.3.91.990629181213.18841Q-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 29 Jun 1999, Mark E. wrote:

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

No, I meant the directory separator, not the drive letter.  If inside 
Bash you have this:

	PATH=/dev/c/foo:/dev/d/bar

then child programs need to see this:

	PATH=c:/foo;d:/bar

I meant the semi-colon that separates the directories.