From: snowball3 AT bigfoot DOT com (Mark E.)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Bash 2.03 beta update
Date: Tue, 29 Jun 1999 17:35:27 GMT
Organization: Snowball's Web
Message-ID: <37790334.769498@news3.ibm.net>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990629181213 DOT 18841Q-100000 AT is>
X-Newsreader: Forte Agent 1.5/32.452
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 129.37.91.5
X-Trace: 29 Jun 1999 17:35:24 GMT, 129.37.91.5
Lines: 22
X-Notice: Items posted that violate the IBM.NET Acceptable Use Policy
X-Notice: should be reported to postmaster AT ibm DOT net
X-Complaints-To: postmaster AT ibm DOT net
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:

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

I understood you to mean that, but I got lazy in my example PATH and didn't
add another directory. The child programs, even when the child is another
instance of Bash, see:
PATH=c:\foo;d:\bar

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