Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Thu, 6 Jul 2000 14:12:03 -0400 To: cygwin@sourceware.cygnus.com Subject: Re: cd .... Message-ID: <20000706141203.A21387@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cygwin@sourceware.cygnus.com References: <3964BB6B399.E1F4SOHDA@matsulab.is.titech.ac.jp> <20000706134323.G20864@cygnus.com> <3964CB41.E558080A@veritas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3964CB41.E558080A@veritas.com>; from rmcgowan@veritas.com on Thu, Jul 06, 2000 at 11:09:05AM -0700 On Thu, Jul 06, 2000 at 11:09:05AM -0700, Bob McGowan wrote: >There is a difference between the Windows handling of this and what >bash/cygwin is doing. Windows cmd (on NT 4.0) appears to ignore the >request. The current directory does not change and cd with no args >gives the same current path as existed before trying the 'cd ...' >command. > >bash/cygwin is "changing" to the specified location, so pwd reports the >'new' path, as was given in the cd request. But an ls shows the >directory contents are the same as for the starting directory, so no >change has actually happened. > >I also found that this only works one level deep for bash/cygwin: > > $ cd ..../.... > bash: cd: ..../....: No such file or directory > >But cmd treats this the same as a single level. > >Are these the expected behaviors? Sigh. No. You're right. Cygwin shouldn't just silently accept this and then act as if nothing was typed. This is probably a recent problem due to the fact that we're caching the POSIX version of the current working directory. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com