open() giving ENOENT when trying to create files with control chars

Brian Dessent
Fri Dec 9 07:50:00 GMT 2005

Yitzchak Scott-Thoennes wrote:

> > Windows strips trailing spaces and dots (unless the file name
> > consists only of spaces).  You need a managed mount to
> > preserve those; otherwise "foo ", "foo.", "foo. . . . ", "foo",
> > and a bunch of other spellings all refer to the same file.
> I attempted to indicate in the message above that I tried it and
> succeeded in using filenames with spaces on the end (and *different*
> files named the same except without the spaces).  It seems this is
> *not* an across-the-board Windows limitation.

This is probably a difference in the win32 API versus the native API.


Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list