Rick Rankin wrote:
There is a funny bug in the 1.5.19 family, maybe in earlier versions too.
[EMAIL PROTECTED] ~
$ cd /usr/.../var
[EMAIL PROTECTED] /usr/.../var
$ ls
ls: .: No such file or directory
FYI, This same behavior is exhibited in the stock 1.5.18-1 release as well, so
this isn't a regression.
It seems you're right, it isn't a regression, but it's still a bug.
cd /usr/..../var (with four dots) works the same way.
You can easily nest those:
$ pwd
/bin/.../bin/.../bin/.../bin/.../bin/.../bin/.../usr/.../usr/.../usr/.../usr/...
/var/.../usr/local/bin/.../src/.../src/.../src/.../src/.../src/.../src/.../src/.
../src/.../src/.../src/.../src/.../src/.../src/.../src/.../src/.../src/.../src/.
../src
$ cd .../src
bash: cd: .../src: File name too long
$ ls
ls: .: No such file or directory
Funny that if I start a windows shell now, it will have the right working
directory (/usr/local/src in this case).
Krzysztof Duleba
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
