Re:CRLF is obsolete and should be abolished
by bityard on Sunday October 13, 2024 @09:02PM
(#41833180)
I have been using and programming Unix systems for almost 30 years and have not run into anything like what you are describing.
What Unix program "throws a fit" when encountering a perfectly normal newline in the last line in a file?
Re:CRLF is obsolete and should be abolished
by perching_aix on Sunday October 13, 2024 @09:17PM
(#41833263)
"Unix programs" I haven't ran into throwing a fit per se. That's why I didn't write that.
What I ran into issues with was contemporary software that's shipped to Linux, such as Neo4j, which expects its license files to have no newline at the end of the file, and will actively refuse to start otherwise.
I have a feeling I'll now experience the "well that's that software's problem then" part of this debate. Just like how software not being able to handle CRLF / CR-only / LF-only, is always the problem - instead of text files being a joke, and platforms assuming things about them being the problem.
I expect my editor to do what I say, not secretly(!) guess what I might have wanted, or will potentially want sometime in the future. Having to insert a newline while concatenating files is a chore, but a predictable annoyance. Having to hunt for mystery bytes, maybe less so.