The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: reed@reedmedia.net (Jeremy C. Reed)
Subject: [TUHS] terminal - just for fun
Date: Wed, 6 Aug 2014 10:26:22 -0500 (CDT)	[thread overview]
Message-ID: <alpine.NEB.2.02.1408060901510.22474@t1.m.reedmedia.net> (raw)
In-Reply-To: <20140806132257.GA23663@mercury.ccil.org>

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?

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.)

When did the sh shell provide intra-line editing?

Were the early Unix versions case insensitive? (Like could I run "DaTe" 
from shell?) If not, how to get the model-33 to work with it?

What about the model-33 printer? Did it print lowercase?

How was the "HERE IS" key programmed? Was it used in Unix?

What was the "REPT" key used for?

I also noticed there wasn't any tilde key. So I looked at some old Unix 
code and didn't see tilde used for home directory until 1980 csh. But 
how was tilde entered for previous uses? (Maybe I just overlooked on 
keyboard.)

Was there any concept of intra-line editing when using a model-33 -- but 
without seeing what is being typed or having it print over (and over) 
same line content? (I should assume that intra-line editing can only 
happen on video terminals.)

(My book in progress explains a lot about the history of ex/vi but 
the earliest version I have is 1.1 which included the support for 
intra-line editing and even visual mode for HP 2645 and LSI ADM-3A 
cursor-addressible terminals. I am hoping my book can also introduce the 
basic usage concepts for readers who have no familiarity with the 
hardware around then. One of the TUHS list participants and termcap/vi 
developer already told me some about the hjkl arrow keys, for example.)



  parent reply	other threads:[~2014-08-06 15:26 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 [this message]
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ć
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=alpine.NEB.2.02.1408060901510.22474@t1.m.reedmedia.net \
    --to=reed@reedmedia.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).