4 ms·
Another thing to watch out for is how you have git configured to handle newlines. Usually the recommended config under Windows is to have it transparently chang
by mcbits 10y ago
Another thing to watch out for is how you have git configured to handle newlines. Usually the recommended config under Windows is to have it transparently change them to \r\n when you clone a project, and back to \n when you push.
This trips up some Linux tools when you use those files from the Linux subsystem. Best either turn that feature off or only use the Linux git for any projects you plan to touch from there, even if you're saving them under /mnt/... to share with Windows. And of course you'll have to beware of how your Windows editors are saving those files.
I wish the Windows world had just migrated to UTF-8 and \n 10 years ago. It would all be smooth sailing by now.
- Const-me 10y agoMost Windows apps, both third-party and built-in, support UTF-8 for many years. Just not by default. You need to specify your data is UTF-8: http://unicode.org/faq/utf_bom.html http://unicode.org/faq/utf_bom.html