The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: milov@cs.uwlax.edu (Milo Velimirović)
Subject: [TUHS] terminal - just for fun
Date: Wed, 6 Aug 2014 11:49:42 -0500	[thread overview]
Message-ID: <84A989CE-4465-4A90-987C-13D0DA71C5F7@cs.uwlax.edu> (raw)
In-Reply-To: <alpine.NEB.2.02.1408060901510.22474@t1.m.reedmedia.net>

I used v6 on an 11/45 -- my comments refer to my recollections from the mid-late 1970s.

On Aug 6, 2014, at 10:26 AM, Jeremy C. Reed <reed at reedmedia.net> wrote:

> On Wed, 6 Aug 2014, John Cowan wrote:
> 
>>> So the model-33 wasn't ASCII?
>> 
>> The keyboard could send all of ASCII except lower-case letters, grave,
>> braces, and vertical bar (i.e. excluding x60 to x7E).  The high-order
>> bit was always set.  Using the paper tape reader and punch, you could
>> transmit arbitrary 8-bit characters.
> 
> I guess it was common to use the Teletype Model 33 independently without 
> any video display. (I read that it could accommodate a modem too.) Did 
> it automatically print to paper everything typed to keyboard in 
> real-time?  Or maybe only when LINE FEED or RE-TURN key was pressed?

What video? I don't recall ever seeing a TTY have video displays.
Terminals could operate in either Full Duplex or Half Duplex. The former required every character to be echoed in order to be printed. In HDX mode every character typed was both sent down the wire and printed.

Yes, some TTYs had an attached acoustic coupler and/or a paper tape reader-punch.

> 
> How would RUB OUT be used when using the sh shell? (I tried looking 
> through the code and manual for some old 32V and previous versions but 
> didn't see code for it yet.)

It wasn't really used. Most often rubout was used on systems where a "text" would be prepared offline and punched on paper tape as it was being typed. Hitting rubout would punch holes in all positions on the tape effectively obliterating  whatever had been typed. Once the offline text was complete the tape could be transmitted to a host for further processing. This was the Automatic Send part of the ASR-33. I recall doing this in the early 70s at a community college I went to -- but this wasn't connected to a UNIX system.

> 
> When did the sh shell provide intra-line editing?

  parent reply	other threads:[~2014-08-06 16:49 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-06  2:56 Doug McIlroy
2014-08-06  6:45 ` arnold
2014-08-06  7:47   ` Dave Horsfall
2014-08-06  9:09     ` Jaap Akkerhuis
2014-08-06 20:43     ` Ronald Natalie
2014-08-06 21:40       ` Mary Ann Horton
2014-08-07  6:44     ` [TUHS] Baudot/ASCII (was Re: terminal - just for fun) Dave Horsfall
2014-08-06 13:22   ` [TUHS] terminal - just for fun John Cowan
2014-08-06 13:44     ` Steve Nickolas
2014-08-06 15:26     ` Jeremy C. Reed
2014-08-06 16:15       ` Armando Stettner
2014-08-06 20:16         ` Jaap Akkerhuis
2014-08-06 20:32           ` Ronald Natalie
2014-08-06 16:37       ` John Cowan
2014-08-06 17:53         ` scj
2014-08-06 19:44           ` A. P. Garcia
2014-08-06 20:36             ` Ronald Natalie
2014-08-06 20:38           ` Ronald Natalie
2014-08-06 16:49       ` Milo Velimirović [this message]
2014-08-06 18:26       ` Mary Ann Horton
2014-08-06 18:48         ` Mary Ann Horton
  -- strict thread matches above, loose matches on Subject: below --
2014-08-04 20:46 Norman Wilson
2014-08-04 21:07 ` Diomidis Spinellis
2014-08-04 19:46 Doug McIlroy
2014-07-31 19:44 Tim Newsham
2014-07-31 22:59 ` Dave Horsfall
2014-08-02 13:30   ` random832
2014-08-01  9:00 ` Dario Niedermann
2014-08-01 15:13   ` Andy Kosela
2014-08-01 15:28     ` Milo Velimirović
2014-08-01 17:50       ` Mary Ann Horton
2014-08-01 17:59         ` Cory Smelosky
2014-08-01 19:59           ` Tim Newsham
2014-08-01 20:11         ` Dave Horsfall
2014-08-01 20:35           ` John Cowan
2014-08-02  1:49             ` Dave Horsfall
2014-08-02  3:27               ` Tim Bradshaw
2014-08-02  3:45                 ` Greg 'groggy' Lehey
2014-08-02  9:24                   ` Tim Bradshaw
2014-08-03  6:47                   ` Dave Horsfall
2014-08-04 18:04                   ` scj
2014-08-04 18:18                     ` Tim Newsham
2014-08-04 18:29                       ` John Cowan
2014-08-04 19:10                         ` Tim Newsham
2014-08-04 19:13                           ` Milo Velimirović
2014-08-04 19:21                             ` Tim Newsham
2014-08-04 18:28                     ` John Cowan
2014-08-05 13:13                       ` arnold
2014-08-05 14:20                         ` John Cowan
2014-08-05 14:46                           ` arnold
2014-08-04 20:15                     ` Jaap Akkerhuis
2014-08-04 20:39                       ` Dave Horsfall
2014-08-02  4:28                 ` Dave Horsfall
2014-08-02  4:46                 ` Warner Losh
2014-08-02 13:22                 ` Nemo
2014-08-02  3:37               ` Greg 'groggy' Lehey
2014-08-02  5:45                 ` Dave Horsfall
2014-08-02  6:09                   ` Greg 'groggy' Lehey
     [not found]               ` <20140802061214.GC13625@mercury.ccil.org>
2014-08-02  6:17                 ` Dave Horsfall
2014-08-02 13:35                   ` Bill Pechter
2014-08-02 14:04                     ` Milo Velimirovic
2014-08-03  2:00                       ` Greg 'groggy' Lehey
2014-08-02 14:30                   ` John Cowan
2014-08-01 21:32           ` Dario Niedermann
2014-08-01 21:38             ` Warner Losh
2014-08-01 21:56               ` Dario Niedermann

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=84A989CE-4465-4A90-987C-13D0DA71C5F7@cs.uwlax.edu \
    --to=milov@cs.uwlax.edu \
    /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).