andybak - A recent change is messing with line ...
A recent change is messing with line feeds in relation to git. @sbanca and @mikesky
10 Replies
should i change core.autocrlf ? it's currently true which worked fine in the past.
I have not change it directly or at least voluntarily but i can see in my local repository is set to false as well
sorry - meant to cc @mikeage not other mike
what's the default for autocrlf on a clean install?
Ok, can you describe the problem?
It came from "Improve Windows development experience (#797)" which was two changes that I pulled out of sbanca's branch
let me do something from the CLI and describe that. I also want to know if it's specific to particular GUIs
ok. I'm going to be offline in a bit for a while, but I'll look when I get back. I believe auto is false by default.
it's happened twice but i can't retrace my steps easily
The changes mean that the tooling will force endings to be LF, which was presumably a reaction to commits getting checked in as CRLF. But if your environment is using CRLF on the working directory, that might be problematic.
i'm pretty sure most editors other that notepad can cope with LF in this day and age
so maybe i should just turn autocrlf off and use LF all the time
(they might have even fixed notepad - it's ages since i checked!)
autocrlf to false would solve some docker issues as well
I think the default is false, so maybe let's try that