> or getting support requests because ignorant users tried to remove that part of the filename and now can't open Word or whatever
Funny side story, windows pops an error confirmation message if you change or remove the extension of a file name as part of a rename operation.
There's no way to disable this message outside of writing an autohotkey script to check for the prompt and auto-accept it. (I did this once, no I don't have the AHK script, but I don't recall it being hard to write.)
On on a similar funny side note, there's no way to tell windows to always open files with no extension in a specified application (e.g. gvim). But you can edit the registry to do it.
Having to deal with other people using it is far more obnoxious than actually personally using it, IMX. For sophisticated users it's not hard to learn these details, and then one naturally just doesn't hit the pitfalls. Teaching the details to someone less sophisticated, and making them stick, is a whole other ball game.
Funny side story, windows pops an error confirmation message if you change or remove the extension of a file name as part of a rename operation.
There's no way to disable this message outside of writing an autohotkey script to check for the prompt and auto-accept it. (I did this once, no I don't have the AHK script, but I don't recall it being hard to write.)
On on a similar funny side note, there's no way to tell windows to always open files with no extension in a specified application (e.g. gvim). But you can edit the registry to do it.