4 ms·
I think one of the main problems is that when you install git for windows, the default setting is to convert LF to CRLF when checking out code. This can cause a
by Mogzol 5y ago
I think one of the main problems is that when you install git for windows, the default setting is to convert LF to CRLF when checking out code. This can cause a bunch of issues if you later try to work with those files within WSL (especially when doing any git-related stuff). I don't really understand why that's the default, or even why it's presented as an option during installation, it's been ages since I actually had issues reading/editing Unix-style files in Windows.
- mey 5y agoIt is insane to me that git doesn't checkout/in as-is by default on Windows.
- fiddlerwoaroof 5y agoThe 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 agobecause of crap like notepad
- stinos 5y agoI always wondered. Source?
- cerved 5y agonotepad is the default text editor in windows, it doesn't support Unix line endings until insider build whatever
- stinos 5y agoSure, but is that really the reason why autocrlf is the default in git?
- zz865 5y agoNotepad 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 agothat'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 agoThe 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.