The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: mah@mhorton.net (Mary Ann Horton)
Subject: [TUHS] Teletype simulator?
Date: Thu, 24 Mar 2016 09:15:49 -0700	[thread overview]
Message-ID: <56F412B5.4010408@mhorton.net> (raw)
In-Reply-To: <201603241440.u2OEeO9p012595@farg.inf.ed.ac.uk>

That sounds like the Teletype model 33, and probably other Teletypes.

If you don't give it the extra .1 second of the LF, the first printed 
character will overstrike in the middle of the line you just typed.  And 
it will be "bold" because the print head is moving very fast to the left.

Normally you'd want the LF to advance, but if you're trying to underline 
by overstriking an underline character, you'd need to pad with a NUL.

The first model 33s I used didn't have an underline.  That character was 
a leftward pointing arrow, which I think was intended to visually show 
backspace, and some systems (GE BASIC, IIRC) used it as an erase 
character.  (Of course, there was no ability to backspace on a 33.)   
The caret printed as an upward pointing arrow, hence it's often called 
"up arrow".

     Mary Ann

On 03/24/2016 07:40 AM, George Ross wrote:
>> Make sure it only prints 10 characters per second, then. (I think TTY's were
>> 10 cps?) R-e-a-l-l-y s-l-o-w.
> And don't forget that carriage-return takes longer than printing individual
> characters, so you need to send CR LF to give it time to get back to the
> first column while it's feeding a line.  Or CR CR LF just in case.
>
> (Or was that the Olivetti terminal?  Or the DECwriter?  One of those
> mechanical things anyway.)
> --
> George D M Ross MSc PhD CEng MBCS CITP, University of Edinburgh,
> School of Informatics, 10 Crichton Street, Edinburgh, Scotland, EH8 9AB
> Mail: gdmr at inf.ed.ac.uk   Voice: 0131 650 5147   Fax: 0131 650 6899
> PGP: 1024D/AD758CC5  B91E D430 1E0D 5883 EF6A  426C B676 5C2B AD75 8CC5
>
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
>
>



  parent reply	other threads:[~2016-03-24 16:15 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 13:19 Noel Chiappa
2016-03-24 14:23 ` Random832
2016-03-24 16:41   ` Jacob Goense
2016-03-24 14:28 ` Lawrence Stewart
2016-03-25 21:27   ` Diomidis Spinellis
2016-03-25 21:56     ` Steffen Nurpmeso
2016-03-28 12:04       ` Steffen Nurpmeso
2016-03-24 14:40 ` George Ross
2016-03-24 15:29   ` Random832
2016-03-24 15:32   ` John Cowan
2016-03-24 16:15   ` Mary Ann Horton [this message]
2016-03-24 20:29     ` scj
2016-03-25 12:54       ` Dave Horsfall
2016-03-26 21:04       ` Ronald Natalie
2016-03-24 19:56 ` scj
  -- strict thread matches above, loose matches on Subject: below --
2016-03-24 20:12 Norman Wilson
2016-03-24 20:24 ` Lyndon Nerenberg
2016-03-24 20:36 ` scj
2016-03-24 13:36 Doug McIlroy
2016-03-23 19:28 [TUHS] PDP-7 Unix: The B compiler works Warren Toomey
2016-03-24  9:01 ` [TUHS] Teletype simulator? Warren Toomey
2016-03-24 10:21   ` Pierre DAVID
2016-03-24 11:00     ` Clem cole
2016-03-24 11:01       ` Clem cole
2016-03-24 21:39       ` Clem Cole
2016-03-25  3:18         ` Mary Ann Horton
2016-03-25  3:57           ` Charles Anthony
2016-03-25 20:13             ` Mary Ann Horton
2016-03-24 16:37   ` Jacob Goense
2016-03-25  2:18   ` Dave Horsfall
2016-03-25  3:43     ` Greg 'groggy' Lehey
2016-03-25  5:59     ` Jacob Goense

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=56F412B5.4010408@mhorton.net \
    --to=mah@mhorton.net \
    /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).