4 ms·
I haven't seen end-of-line conversion problems (as well as Unicode BOMs) for decades. My guess is that software quality improved these days. MS Notepad was a no
by ktpsns 2y ago
I haven't seen end-of-line conversion problems (as well as Unicode BOMs) for decades. My guess is that software quality improved these days. MS Notepad was a noteable tool which always mocked around with unix-style line endings. Using dos2unix and unix2dos utilities was something I commonly used in the early 2000s, in particular on dual boot computers. This was also the time where UTF-8 was not yet so widespread, but that is another topic ;-)
- don-code 2y agoSad to say, I filed a bug in an internal tool just two weeks ago relating to how it processes Windows linebreaks. The tool is written using modern languages (Python 3.11) and frameworks (FastAPI).
- yjftsjthsd-h 2y agoI can easily believe that it's gotten better, but I've hit it within the last 6 months; Microsoft Azure DevOps git[0] has a web editor that defaults to Windows-style EOL, and if you use it to deploy files to boxes running a Linux distro then some tools will completely break on config files that aren't using unix-style EOL. Ask me how I know. That was fun to fix. For bonus points, some programs on Linux are compatible with either line ending-_- [0] I expect this isn't its real name, but it's MS so that's a lost cause.