Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#30 Windows file name restrictions

open
nobody
Other (11)
5
2003-12-27
2003-12-27
Aaron Hamid
No

After going crazy trying to figure out why a checkout
was not working, I discovered this Windows idiosyncrasy:

http://www.codeproject.com/file/isvalidfilename.asp?
print=true

Apparently there are some 'reserved' file names in
Windows which cannot be created, deleted, or otherwise
manipulated. This includes:

CLOCK$, AUX, CON, NUL, PRN, COM1, COM2, COM3,
COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2,
LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9

It so happened that 'aux' was the name of one of the
directories in the project I was checking out, and
because Gruntspud could not create it, it summarily
exited with an error.

I realize that this is fundamentally a stupid Windows
peculiarity, but I think it would be rather trivial to
recognize and either put up a warning dialog, or take an
alternate name, or just prepend underscore or something
like that, so the user is aware of the problem and is able
to work around it.

I will also file this as a BUG.

Discussion