The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: pete@dunnington.plus.com (Pete Turnbull)
Subject: [TUHS] Line Terminators in Text Files [Was: Re: Why Pascal is Not My Favorite Programming Language - Unearthed!]
Date: Mon, 4 Sep 2017 01:31:22 +0100	[thread overview]
Message-ID: <2c69951c-964d-0ab3-4494-dbe38d90aa3c@dunnington.plus.com> (raw)
In-Reply-To: <201709032314.v83NEhxg031354@elf.torek.net>

On 04/09/2017 00:14, Chris Torek wrote:

> In what was either a remarkable coincidence, or actual planning,
> the old ASR 33 at I think 110 baud (maybe 300) took two "character
> times" to do the carriage return, so that if you sent CR and LF
> in that order, the LF occurred mid-CR and the print head was
> ready right at the time the next character arrived.

That's not right.  Yes, the ASR33 runs at 110 baud (10cps), but all - 
including mine and those of my friends -  take more like half a dozen 
character times to perform a CR from the right hand side.  Moreover, the 
time it takes depends in a non-linear fashionon how far along the line 
the printhead has travelled; it's driven by a spring and decelerated and 
stopped by an air dashpot.  Even an LF takes more than two character 
times.  That's why ASR33 drivers send a string of nulls after a CR. 
Many are smart enough to send the LF instead of the first null, if they 
see that LF is the first character after CR.

>> 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 ASR33 friction feed models, but not the sprocket fed ones, can be 
configured to do that but AFAIR only at the 72nd character position at 
the end of a line.

> Possibly, since as I recall there was a keyboard key that did the
> equivalent of pushing the return bar on a manual typewriter.  If
> you look at photos of Selectrics, there is no external bar (though
> of course there are knobs to rotate the platen for inserting and
> removing pages).

That's correct.  Selectrics have a RETURN key, which performs carriage 
return and linefeed, and on mine there was a switch for single/double 
line spacing too.  I no longer have one, but I used to have two.

-- 
Pete
Pete Turnbull


  parent reply	other threads:[~2017-09-04  0:31 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
2017-09-03 23:14     ` Chris Torek
2017-09-03 23:37       ` Grant Taylor
2017-09-04  0:31       ` Pete Turnbull [this message]
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=2c69951c-964d-0ab3-4494-dbe38d90aa3c@dunnington.plus.com \
    --to=pete@dunnington.plus.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).