bash "cd" bug when pathname has 3+ periods

[Sergey Okhapkin]

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@cygnus.com" with one line of text: "help".