This is the mail archive of the
mailing list for the Cygwin project.
Re: Strange cd/CDPATH behavior
- To: cygwin at sources dot redhat dot com
- Subject: Re: Strange cd/CDPATH behavior
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Tue, 26 Sep 2000 19:52:36 -0400
- References: <email@example.com>
- Reply-To: cygwin at sources dot redhat dot com
On Tue, Sep 26, 2000 at 01:16:47PM -0700, Earnie Boyd wrote:
>--- Chris Faylor <firstname.lastname@example.org> 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
>> 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.
Want to unsubscribe from this list?
Send a message to email@example.com