4 ms·

It is insane to me that git doesn't checkout/in as-is by default on Windows.

• fiddlerwoaroof 5y ago
  The biggest gotcha on Mac is using git on the default case-insensitive volume. I always create a separate case-sensitive APFS volume for all my git repos to avoid subtle mismatches between the filename git knows about and the filename macOS knows.
• cerved 5y ago
  because of crap like notepad
  • stinos 5y ago
    I always wondered. Source?
    • cerved 5y ago
      notepad is the default text editor in windows, it doesn't support Unix line endings until insider build whatever
      • stinos 5y ago
        Sure, but is that really the reason why autocrlf is the default in git?
        • cerved 5y ago
          it's the default in git-for-windows I see no other reason that maximum platform compatibility
          • stinos 5y ago
            Would be weird if platfrom compatibility is measured by making sure once single program works, a program which most of the people using git probably don't even use
      • zz865 5y ago
        Notepad changed 3 years ago so now this isn't a problem. Git should default everything to LF. https://devblogs.microsoft.com/commandline/extended-eol-in-notepad/ https://devblogs.microsoft.com/commandline/extended-eol-in-n...
        • cerved 5y ago
          that's a Windows 10 insider build, git for windows presumably wants to be more backwards compatible just change it to input and be happy
          • Mogzol 5y ago
            The new notepad version was released to non-insiders in Windows 10 1809, so it's still been around for almost 3 years now. I do understand that git wants to maintain the best compatibility, but at this point I would argue that converting to CRLF on checkout is causing more issues than it solves.