Subject: bash "cd" bug when pathname has 3+ periods
From: [email-masked] ("Daniel J. Barrett")

9 Jul 1997 17:40:40 -0700
Sender: [email-masked]
Approved: [email-masked]
Distribution: cygnus
Message-ID: <[email-masked]>
Reply-To: [email-masked]
Original-To: [email-masked]
Original-cc: [email-masked]
Original-Sender: [email-masked]

	In Bash 1.14.7(2) under Windows 95, the Bash command "cd"
exhibits incorrect behavior.  This bug does not occur in bash compiled
for UNIX.

	Run "cd" with a pathname that does not exist, and whose last
component is 3 or more periods.  Here are some examples:

	cd ...
	cd /....
	cd /foo/bar/.....

Bash will "cd" into the nonexistent directory.  For example:

        $ pwd
        /
        $ cd ...
        $ pwd
        /...

I did not compile this bash -- I downloaded the binary from ftp.cygnus.com
today as part of USERTOOLS.EXE.

--
Dan Barrett
[email-masked]

-
For help on using this list (especially unsubscribing), send a message to
"[email-masked]" with one line of text: "help".