Hacker News Reader

Comment by danielvaughn | Hacker News Reader

yep, I still don't use spaces. I also don't use uppercase characters. Just underscores or hyphens.

Sometimes I break the rule and use uppercase but never spaces.

I've had issues when moving between Window/*nix file systems, where Windows file names are case insensitive and *nix systems are case sensitive.

Build script works fine locally on Windows, but then chokes in *nix test server, as it's effectively a different path.

file names aren't case insensitive, it's the windows API that is

I assume you mean that the Windows API (standard for Windows apps) is case insensitive, but if using the WSL (Windows Subsystem for Linux) it's possible to get case sensitivity: https://docs.microsoft.com/en-us/windows/wsl/case-sensitivit...

Even if you're not using WSL, you've always been able to turn on case sensitivity via a registry key. This has not been recommended in the past due to possible issues with windows itself as well as third party software. This history is mentioned here[0]. Everywhere that mentioned a registry key seems to be referring to windows nfs server, not to general file access, however I know that SFU (Services for Unix) installer had an option to do so, so it's certainly possible.

As of sometime in 2018, fsutil can set specific directory trees to be treated case sensitive in Windows 10 without setting it for the OS. This ability is mentioned here[1]

[0]: https://devblogs.microsoft.com/commandline/per-directory-cas... [1]: https://docs.microsoft.com/en-us/windows/wsl/case-sensitivit...

I’ve had issues with git when changing a filename, if the only change is the casing.

Reply on news.ycombinator.com