This is the mail archive of the
mailing list for the Cygwin project.
Re: cd accepting paths with trailing dots that don't exist (bash and tcsh)
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: "'cygwin at cygwin dot com'" <cygwin at cygwin dot com>
- Date: Tue, 10 Dec 2002 17:18:59 +0100
- Subject: Re: cd accepting paths with trailing dots that don't exist (bash and tcsh)
- References: <D721826DEE793D49BC49582C121EDD3E7FF5@exchange.perwill.com>
- Reply-to: cygwin at cygwin dot com
On Tue, Dec 10, 2002 at 03:49:24PM -0000, Steve Fairbairn wrote:
> Corinna & All,
> After a play with a dos command prompt, I see your point. I would however
> point out that there is still a difference with bash. If you have more than
> one trailing . in bash, the 'directory' it puts you in is empty, and you
> cannot create any files in there. Also bash seems to retain the trailing
> dots as part of your cwd, which the dos prompt doesn't do. With the dos
> prompt, it just seems to strip the trailing dots off, and always leave you
> in the directory you trailed with dots.
> As for "correct functionality" I meant whatever the cygwin developers define
> as correct. My personal preference would be for bash to complain about the
> trailing dots, but I understand that the shell probably just uses the
> Windows OS chdir function, and so it is Windows deciding the path is valid.
> Would there be massive overhead in bash re-reading the cwd after a
> successful chdir, and so not display the dots? How come ls etc doesn't work
> if there is more than one trailing dot?
Weird. Works for me. I can create a dir "a.b" with files in it and
then cd into "a.b....." and I can see the files. I'm running tcsh, though.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:email@example.com
Red Hat, Inc.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html