3 ms·
The post mentions CRLF line end syntax, I don't understand why anyone should bother with it. Use \n only, it works everywhere including Windows. Any modern IDE
by codedokode 4y ago
The post mentions CRLF line end syntax, I don't understand why anyone should bother with it. Use \n only, it works everywhere including Windows. Any modern IDE can handle Unix line endings. The same about file paths, use forward slash (/) everywhere and don't waste your time supporting DOS era standards.
I think the core.autocrlf option in Git is more harmful than useful (for example, it can change file hashes and break something) and should be removed. An option to warn about unwanted \r characters on commit might be useful though.
- deleted 4y ago[deleted]
- Shorel 4y ago> I think the core.autocrlf option in Git is more harmful than useful Nowadays, I am willing to agree with you. It breaks more things than fixes them.
- moogly 4y agoAgreed. autocrlf = input Then change your editors and IDEs to save files with LF line endings (preferably with something like .editorconfig) and you'll have fewer problems.