💾 Archived View for rawtext.club › ~sloum › geminilist › 000951.gmi captured on 2020-11-07 at 01:52:41. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
Brian Evans b__m__e at mailfence.com
Thu May 21 22:28:01 BST 2020
- - - - - - - - - - - - - - - - - - -
In the CR, LF , and CRLF debate I find myself in favor of not worrying about the relic that is CR only. No modern systems use thisand as a new protocol I dont see a compelling reason to support ancient systems.Particularly given that even among ancient systems just a CR as a line endingwas a rarity.
(The below quote has been edited to provide the character that was actuallymeant, per solderpunk's later post):
Bombadillo and Castor (an old build of Castor I had lying around,
admittedly) both handled LF and CRLF fine, but did not split CR lines at
all.
Bombadillo should be able to handle two of the three. For dealing with linesI split on newline and remove trailing whitespace from all lines when rendering.Bombadillo will also never render a `\r` character (the line wrapping parses themout of the render for display purposes). I imagine Castor and Asuka are doing something vaguely similar.
Some quick experimentation with Python revealed that str.splitlines()
is, indeed, smart enough to handle CRLF, CR and LF as linebreaks.
That _is_ pretty cool that the python method was able to detect \r line endingsand split them though. Points to python on that one.