Quote:
Originally Posted by Renate
Early teleprinters (like the Teletype Model 15) used a fixed platen, a moveable carriage. The original 5 bit Baudot code had been extended to work with typewriter-like devices (instead of printing paper stripes). Two control codes were added, Carriage Return and Line Feed. These were regarded as independent movements. Moving the heavy carriage back 8 inches took a lot of time in contrast to rolling the platen 1/6 of an inch. So CR always preceded LF.
In modern usage LF has been rebranded New Line and implicitly includes a CR. Unless you're overprinting a single line there is no reason to use anything besides LF (NL). For command line text usage of dynamic statistics Backspace is used to redo a field. — dynamic statistics, redo a field, in a command line — eh what 
Most programs that accept text can handle CR/LF or LF. Apple decided to use just CR for a while which really messed things up. Using just a single code for the logical end of a line makes sense. Unfortunately there are still standards that explicitly require CR/LF like HTTP/HTTPS. All headers for the web are required to have CR/LF although the content can switch to just LF.
Phew. That's a long one. Do people like it more when I break it into lines or leave it free flowing?
|
A wall of text is anything but 'free flowing'.
They discourage self editing as-you-go by the writer - see example above. And they give no hint to the reader to ask 'did I get that"- and if not go back and reread. And they encourage TL:DR responses.
Now, how come there's no Miller Column add-on for Windows File Explorer - only want it occasionally.
BR