On the TOPS-10 side, the use of CRLF goes back to the PDP-6 Monitor OS. (Before
that I have no idea.) This takes us back to 1965. Except that it wasn't
precisely CRLF - in some cases you were allowed to omit the CR on the second
and subsequent blank lines.
I think this died out fairly quickly, but I recall seeing code to accomodate it
in some CUSP (commonly used system program) or other.
AFAIK Tenex copied TOPS-10 in this area.
Ned
In article <d73baf1d-ef7f-7c0e-1e5e-10d8ba748af7(_at_)pscs(_dot_)co(_dot_)uk>
you write:
CR takes you back to the start of the current line, and LF takes you to
the next line (at the current position), ...
Except when it doesn't. In 1969 when people at Bell Labs were writing
the early versions of Unix, they had a lot of the otherwise obscure
Model 37 Teletype, which had upper and lower case and where the 012
character was a new line (NL), moving the print position to the
beginning of the next line. It had unusually sophisticated buffering
for the era and didn't need any delay characters. Teletype was an
AT&T subsidiary so it's not surprising that the Labs would get early
versions of their products.
Other places the models 33 and 35 were the most popular terminals,
both of which needed CR/LF to print properly. But as Dave noted, we
had to pick some line end convention and given how common CR/LF was at
the time, it was as good a convention as any.
Even the earliest Unix systems had tty drivers that could adapt to
model 33 or 35, adding CR in front of NL and providing escapes to
enter lower case letters and other characters not on the keyboard.
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp