The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: scj@yaccman.com (Steve Johnson)
Subject: [TUHS] Line Terminators in Text Files [Was: Re: Why Pascal is Not My Favorite Programming Language - Unearthed!]
Date: Sun, 03 Sep 2017 15:28:06 -0700	[thread overview]
Message-ID: <cfb786623cc4a7df90c6009394bfff527b31f440@webmail.yaccman.com> (raw)
In-Reply-To: <alpine.BSF.2.21.1709031252120.48526@aneurin.horsfall.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2034 bytes --]

I think the reason for this is pretty obvious.  At the time -- for
many of the paper terminals, line feed simply rotated the platen, and
the print head stayed at the same column position.  Carriage return
returned the print head to the first column without advancing the
paper (remember overstriking?).  But there were also some terminals
that both advanced the paper and returned the print head (I'm hazy
about this, but I think the IBM Selectric was one...).

The Honeywell system in Murray Hill had a teletype driver that
attempted to paper over these differences.  If it saw a linefeed on
some tty's they would issue the line feed and then space out to the
previous column location.   If it saw a carriage return it would
backspace to the first column.  It did recognize CR/LF and did
something more reasonable.

I do remember one guy who wrote his program to output LF/CR instead of
CR/LF.   The teletype driver would do a LF and then space out to the
previous column and then do a carriage return.  Pretty painful at 300
baud!

Doug might remember better than I but I suspect some terminal did the
combined CR/LF only, so that's why Unix adopted it.  Certainly by the
time glass teletypes came along, making overstriking (and often
underlining) impossible, I don't think anybody objected.

Steve

----- Original Message -----
From: "Dave Horsfall" <dave@horsfall.org>
To:"The Eunuchs Hysterical Society" <tuhs at tuhs.org>
Cc:
Sent:Sun, 3 Sep 2017 12:54:02 +1000 (EST)
Subject:Re: [TUHS] Line Terminators in Text Files [Was: Re: Why Pascal
is Not My Favorite Programming Language - Unearthed!]

 On Sat, 2 Sep 2017, Nemo wrote:

 > Hhhmmm... This begs the historical question: When did LF replace
CR/LF 
 > in UNIX?

 Unix has always used NL as the terminator :-)

 -- 
 Dave Horsfall DTM (VK2KFU) "Those who don't understand security will
suffer."

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170903/a84e58a5/attachment.html>


  parent reply	other threads:[~2017-09-03 22:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-03  2:08 Nemo
2017-09-03  2:54 ` Dave Horsfall
2017-09-03 15:08   ` Warner Losh
2017-09-03 22:28   ` Steve Johnson [this message]
2017-09-03 23:14     ` Chris Torek
2017-09-03 23:37       ` Grant Taylor
2017-09-04  0:31       ` Pete Turnbull
2017-09-04  1:47         ` Chris Torek
2017-09-04  2:58           ` Warner Losh
2017-09-04  9:05             ` Pete Turnbull
2017-09-04 15:33             ` Chris Torek
2017-09-04 10:07           ` Pete Turnbull
2017-09-05 15:23             ` Paul Winalski
2017-09-05 15:37               ` Clem Cole
2017-09-05 18:55         ` Paul Winalski
2017-09-05 19:13           ` Pete Turnbull
2017-09-04 17:44     ` Paul Winalski
2017-09-04 20:30       ` ron minnich
2017-09-04 20:41         ` Bakul Shah
2017-09-04 22:44 Noel Chiappa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cfb786623cc4a7df90c6009394bfff527b31f440@webmail.yaccman.com \
    --to=scj@yaccman.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).