May 17, 2020 3:55 PM, "Felix Quei?ner" <felix at masterq32.de> wrote: > Why does gemini use <CR><LF> line endings instead of a single <LF> or > <CR> token? It makes the parser implementation more complex and imho > brings no benefit to the protocol and text format itself. <CR><LF> is the windows line ending, also HTTP spec for example, requires that no idea why it's required, exactly functionally you could just split on <LF> and remove all <CR> occurrences, I think. CR, the carriage return, would return the cursor to the start of the line, which is almost certainly not wanted in the middle of the text (also ancient macOS, before OS X, used ONLY <CR>, iirc, as a fun sidenote) using <CR><LF> would allow you to directly netcat from windows, or so, I suppose... I'd think it would be best if the server side would accept either <CR><LF>, AND only a normal <LF> and I'm not sure it really matter what the server returns, because you can strip out all <CR> characters, and on linux (probably all unixes?) it displays like a normal newline anyway
---
Previous in thread (1 of 5): 🗣️ Felix Queißner (felix (a) masterq32.de)
Next in thread (3 of 5): 🗣️ solderpunk (solderpunk (a) SDF.ORG)