question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ship core.autocrlf=true value in dugite-native for Windows

See original GitHub issue

This was a useful feature in GitHub for Windows, which was built on an internal version of msysgit and, as such, had its own global Git configuration that could have autocrlf globally defaulted on.

It looks like GitHub Desktop is designed to only respect .gitattributes in a repository for CRLF handling (initializing every repository it creates with one); it would be nice if there were an option to enable automatic CRLF translation when .gitattributes is not present (an option that, I would add, should be enabled by default, as it was in GitHub for Windows), as I have a lot of existing repositories without .gitattributes that expect the platform’s Git client to manage this itself (a reasonable expectation that, again, was followed by For Windows).

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:21 (10 by maintainers)

github_iconTop GitHub Comments

2reactions
shiftkeycommented, Jan 22, 2018

@stuartpb we had a long discussion about this in #340 and added steps to get Git for Windows as close to Git Shell as possible in https://github.com/desktop/desktop/issues/340#issuecomment-302021683. We’ve decided to focus our resources on the UI side of Git and help support upstream efforts wherever possible, rather than competing with Git for Windows.

0reactions
stuartpbcommented, Jan 22, 2018

I just installed Git for Windows (with its autocrlf config), and I’m still seeing the out-of-place warnings I described earlier (saying line endings have changed specifically for files where they haven’t). I’ll file a new issue with repro steps for that.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Git: autocrlf=true core.eol=native vs autocrlf=input
Setting this variable to "true" is the same as setting the text attribute to "auto" on all files and core.eol to "crlf". Set...
Read more >
CRLF vs. LF: Normalizing Line Endings in Git
Both of these options enable automatic line ending normalization for text files, with one minor difference: core.autocrlf=true converts files to ...
Read more >
Gits CRLF handling is the source of all modern CRLF woes : r/git
Autocrlf should default to false and the attributes file default behavior should be * text eol=lf even on windows. I develop on Windows...
Read more >
Visual studio uses wrong default for git config core.autocrlf
autocrlf default set as 'true', checking out all text files with CR+LF, and checking in them back with LF. Command line git uses...
Read more >
Mind the End of Your Line - Adaptive Patchwork
core.autocrlf = true This means that Git will process all text files and make sure that CRLF is replaced with LF when writing...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found