Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 20 May 2005 16:25:05 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Path problems with trailing dot Message-ID: <20050520202504.GA11587@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <428897C6 DOT 5050508 AT byu DOT net> <20050516141934 DOT GD15318 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050516141934.GD15318@trixie.casa.cgf.cx> User-Agent: Mutt/1.5.8i On Mon, May 16, 2005 at 10:19:34AM -0400, Christopher Faylor wrote: >On Mon, May 16, 2005 at 06:53:26AM -0600, Eric Blake wrote: >>According to Stefan Schuerger on 5/15/2005 4:41 PM: >>>bash: test./test2: No such file or directory >>> >>>The trailing dot disappears and cannot be used in paths. This seems to >>>be a DOS legacy of either NTFS or Windows. >> >>Yes - Windows strips all trailing spaces and dots. So `mkdir test.' >>and `mkdir test' are identical in behavior in creating `test/', unless >>you use managed mounts (where cygwin does some magic to overcome the >>Windows limitations). >> >>It looks like the cygwin path-normalization code is not stripping >>trailing dots/spaces from non-final directory components in a >>non-managed path name. Care to contribute a patch? >>http://cygwin.com/acronyms/#SHTDI > >Sorry, but it's not that simple. > >We're discussing this in cygwin-developers now. We'll have some kind >of resolution in 1.5.17. Btw, recent snapshots should cause test./test2 to be equivalent to test/test2 . This will be the behavior in 1.5.17. cgf -- 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/