We must settle the line endings debate once and for all

we must settle the line endings debate once and for all

\r\n


or

\n

Attached: Newline_hex_0A.png (832x478, 91K)

I am using C and C++

\r\n

\n

\n\r

technically this makes the most sense.

that's why no one uses it

let's make it the standard. we can do this Jow Forums

\n
even on windows, all the text editors I use accept \n

That just sounds wrong -- it's \r\n because \r would physically move on a teletype, so when \n was received, it didn't matter that the carriage was still moving, all it did was move the page and not print anything.
If it was \n\r, you'd move down, then the carriage would move...
...and then any character immediately after has a decent chance of being typed somewhere randomly in the middle of the page since it probably hadn't finished moving.

NL (NEL U+0085 in unicode)

forgot to attach image

Attached: NL.png (1157x342, 64K)

\r\n in Windows, \n in Lunix. No need to thank me.

I've never used a tty but the typewriters I did use all moved the paper first, then the carriage. So \r\n seems wrong to me. Also I expect a tty would have some kind of input buffering to avoid striking while the carriage is still in motion.

/n

\n

There's no need to waste another byte on every new line, that's bloat.

\n
\r\n is antiquated shit that came from typewriters

/n anything else just prove you are a shitskin and should stay away from a computer.

\r

Neither. Just \r.

/n/i/g/g/e/r

Did you mean with \'s?

Transportation. Oekaki. Technology. Ecchi. Request. By our powers combined, I am /n/i/g/g/e/r/

Attached: Captain-Planet1-700x300.jpg (700x300, 42K)

>input buffering
considering how just old the sequence is, probably not

5c 6e (\\n)

chr(10)

\n because we aren't on typewriters anymore.

Since the whole thing is synchronous, all you need to do is not acknowledge until the carriage is in the home position. No buffer required.

There's no debate, retard.