Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
From: Chris Faylor <cgf@cygnus.com>
Date: Tue, 26 Sep 2000 15:29:43 -0400
To: cygwin@sourceware.cygnus.com
Subject: Re: Strange cd/CDPATH behavior
Message-ID: <20000926152943.B5079@cygnus.com>
Reply-To: cygwin@sources.redhat.com
Mail-Followup-To: cygwin@sourceware.cygnus.com
References: <20000926181915.7663.qmail@web118.yahoomail.com> <012101c027ef$a6916f70$c4acb018@home.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.6i
In-Reply-To: <012101c027ef$a6916f70$c4acb018@home.com>; from enolte@campuspipeline.com on Tue, Sep 26, 2000 at 01:26:20PM -0600

On Tue, Sep 26, 2000 at 01:26:20PM -0600, Erik Nolte wrote:
>B20.1 must have recognized that w:/ is an absolute path while 1.1.4 doesn't
>think so.  And somehow "." in CDPATH triggers the problem.

It is *not* B20.1 that is an issue here.  It is *bash*.  There are (obviously)
different versions of bash in older cygwin releases than there were in
newer releases.

Rather than endlessly speculating about this, can someone look at the code and
find out what is going on???  I sincerely doubt that there will be a simple
workaround for this problem that does not involve changing bash.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com