From:	sos AT prospect DOT com DOT ru (Sergey Okhapkin)
Subject:	RE: bash "cd" bug when pathname has 3+ periods
10 Jul 1997 02:17:17 -0700 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<01BC8D2A.1CDB7AE0.cygnus.gnu-win32@sos>
Original-To:	"gnu-win32 AT cygnus DOT com" <gnu-win32 AT cygnus DOT com>,
	"'barrett AT cs DOT umass DOT edu'" <barrett AT cs DOT umass DOT edu>
Encoding:	20 TEXT
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Daniel J. Barrett wrote:
> 
> 	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/.....
> 

Try the same with command.com's cd :-) It's a feature of win95...

-- 
Sergey Okhapkin, http://www.lexa.ru/sos
Moscow, Russia
Looking for a job

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -