This is the mail archive of the
mailing list for the Cygwin project.
Re: Path problems with trailing dot
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 16 May 2005 10:19:34 -0400
- Subject: Re: Path problems with trailing dot
- References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA9qlOdnHM3EGvlIpcXSWiJ8KAAAAQAAAAB4H/ACBmmUuuyUsddSpBHAEAAAAA@gmx.de> <428897C6.email@example.com>
- Reply-to: cygwin at cygwin dot com
On Mon, May 16, 2005 at 06:53:26AM -0600, Eric Blake wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>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
>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.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html