Can't create files/folders ending in dot (.) character...

[somethingthatrhymes]

I can't create a folder ending in a dot. Windows doesn't complain, it simply renames the folder without the dot, without telling me.

I've tried the usual "do it in command prompt" with echo > , rename, and mkdir. I've created it in Linux (neither FAT nor NTFS complain), but as soon as Windows sees the folder, it just goes ahead and removes the dot!

What's the deal? Is there a way to bypass this and create a folder with a trailing dot? Why does MS do these silly things? (I actually am pretty interested in the reasoning behind this)

EDIT: Google shows me some people that have files/folders ending in dots are having troubles deleting them, but doesn't tell me how to create them. (I'm not worried about deleting them afterwards - I can just use Linux, which handles them sanely, or whatever voodoo that those people out there are using)

Edited November 12, 2007 by somethingthatrhymes

[Will L]

On 11/12/2007 at 4:10 PM, BudMan said:

I have to wonder WTF you would want to do this for?

http://msdn2.microsoft.com/en-us/library/aa365247.aspx

Naming a File

Naming Conventions

The following rules enable applications to create and process valid names for files and directories regardless of the file system:

# Do not end a file or directory name with a trailing space or a period. Although the underlying file system may support such names, the operating system does not. You can start a name with a period (.).

Windows is designed for manual point-and-click mechanics, which creates conflict and friction for those of us who develop software. Example: https://github.com/ropensci/drake/issues/1147. Here, the user does not deliberately try to create a file ending with a dot, but the software needs one anyway. This is just one of many edge cases caused by strange Windows file name restrictions. Fine for point-and-click Windows users,    frustrating for developers.

Edited January 25, 2020 by Will L

[+BudMan MVC]

I have to wonder WTF you would want to do this for?

http://msdn2.microsoft.com/en-us/library/aa365247.aspx

Naming a File

Naming Conventions

The following rules enable applications to create and process valid names for files and directories regardless of the file system:

# Do not end a file or directory name with a trailing space or a period. Although the underlying file system may support such names, the operating system does not. You can start a name with a period (.).

[somethingthatrhymes]

Well basically I just want to do it for compatibility between OSes.

Although the underlying file system may support such names, the operating system does not.

But... WHY?!?!? It's _just another character_. There shouldn't be anything special about dots. In *nix, filenames can contain anything but NULL (yes, even \t, \n, etc.), since it's the string terminator. I'm just baffled by why dots are so bad.

[night_stalker_z]

There are quite a few names or characters which Windows wont let you use like the dot at the end. Its probably due to the incompatibilties between Windows XP/Vista and Windows 95/98.

[Fred Derf Veteran]

But... WHY?!?!? It's _just another character_. There shouldn't be anything special about dots. In *nix, filenames can contain anything but NULL (yes, even \t, \n, etc.), since it's the string terminator. I'm just baffled by why dots are so bad.

There are a great many characters that are not allowed including question marks, apostrophes and various slashes. Windows still has many of the original DOS limitations (something that now dates back multiple decades). It's just there. Live with it.

[adrynalyne]

1 hour ago, Will L said:

Windows is designed for manual point-and-click mechanics, which creates conflict and friction for those of us who develop software. Example: https://github.com/ropensci/drake/issues/1147. Here, the user does not deliberately try to create a file ending with a dot, but the software needs one anyway. This is just one of many edge cases caused by strange Windows file name restrictions. Fine for point-and-click Windows users,    frustrating for developers.

Only 12+ years too late. 

[Paralegal]

 

On 24/01/2020 at 20:47, Will L said:

Windows is designed for manual point-and-click mechanics, which creates conflict and friction for those of us who develop software. Example: https://github.com/ropensci/drake/issues/1147. Here, the user does not deliberately try to create a file ending with a dot, but the software needs one anyway. This is just one of many edge cases caused by strange Windows file name restrictions. Fine for point-and-click Windows users,    frustrating for developers.

 

On 24/01/2020 at 22:13, adrynalyne said:

Only 12+ years too late. 

Google took me here 13+ years too late and I found Will's post helpful. Thanks

[adrynalyne]

@Steven P.Why is this still open? I thought these things auto-close after a certain amount of time. I don’t recall the length, but I think 13 years is quite enough. 😜

[Steven P. Administrators]

20 minutes ago, adrynalyne said:

@Steven P.Why is this still open? I thought these things auto-close after a certain amount of time. I don’t recall the length, but I think 13 years is quite enough. 😜

Because people like you keep bumping it after someone else replies  

[adrynalyne]

6 minutes ago, Steven P. said:

Because people like you keep bumping it after someone else replies  

Cute. I’m just pointing out this isn’t working right.

Edit: Ah it’s so close to the 24th one year later. 
 

Still, you reply and still leave it open? 
 

Lazy. 

[Marujan]

no

[Steven P. Administrators]

57 minutes ago, adrynalyne said:

Cute. I’m just pointing out this isn’t working right.

Edit: Ah it’s so close to the 24th one year later. 
 

Still, you reply and still leave it open? 
 

Lazy. 

Butthurt much? 😛 

[adrynalyne]

10 minutes ago, Steven P. said:

Butthurt much? 😛 

You set a great example. I tagged you because I thought something wasn’t working and you act like a...nah, I’ll avoid the warning.