Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: Chris Faylor Date: Tue, 26 Sep 2000 19:52:36 -0400 To: cygwin AT sources DOT redhat DOT com Subject: Re: Strange cd/CDPATH behavior Message-ID: <20000926195236.E6082@cygnus.com> Reply-To: cygwin AT sources DOT redhat DOT com Mail-Followup-To: cygwin AT sources DOT redhat DOT com References: <20000926201647 DOT 2061 DOT qmail AT web108 DOT yahoomail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <20000926201647.2061.qmail@web108.yahoomail.com>; from earnie_boyd@yahoo.com on Tue, Sep 26, 2000 at 01:16:47PM -0700 On Tue, Sep 26, 2000 at 01:16:47PM -0700, Earnie Boyd wrote: >--- Chris Faylor wrote: >> 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. >> > >Well, actually, the changes to allow Cygwin to recognize d:/ as a Win32 >absolute path have IMO caused the change. I doubt it. There was no change in Cygwin with respect to d:/foo other than to avoid trying to resolve d:/foo through cygwin's mount table. This seems like it is very much a bash problem. Regardless, the first line of attack is to see what bash is doing and stop talking about it. I will do the latter and hopefully someone to whom this matters will do the former. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com