From: Paul Winalski <paul.winalski@gmail.com>
To: Ronald Natalie <ron@ronnatalie.com>
Cc: segaloco <segaloco@protonmail.com>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: UNIX Influence on Teletype and Vice Versa
Date: Mon, 18 Sep 2023 14:27:01 -0400 [thread overview]
Message-ID: <CABH=_VQBS9hT-Y+7-u-VPM1pZVTuLxUr005WsGh6qP9hyH97-Q@mail.gmail.com> (raw)
In-Reply-To: <em9c0d2174-8c9c-45c3-a11b-023503874371@1984688d.com>
On 9/18/23, Ronald Natalie <ron@ronnatalie.com> wrote:
> The thing most people know in the (computer) world as a teletype is a
> model 33 which really UNIX was unaffected by (other than dealing with
> the limited character set) and UNIX didn’t influence. For those with a
> model 37 (I had one in my house for a while picked up surplus from Rocky
> Flats), you knew of its influence on UNIX. This was a unit that the
> line terminator was indeed NEWLINE (^J) rather than carriage return. It
> dealt with all the ESC 8 and 9 and the like that nroff put out by
> default and th SI/SO to shift from the regular to the greek character
> box.
Most importantly for Unix, I would think, the Teletype model 37 had
both uppercase and lowercase capability. Essential for a
case-sensitive environment such as Unix. The model 33 was
uppercase-only.
-Paul W.
next prev parent reply other threads:[~2023-09-18 18:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 18:07 [TUHS] " segaloco via TUHS
2023-09-18 18:21 ` [TUHS] " Ronald Natalie
2023-09-18 18:27 ` Paul Winalski [this message]
2023-09-18 20:02 Douglas McIlroy
2023-09-22 1:08 Douglas McIlroy
2023-09-22 1:14 ` Larry McVoy
2023-09-22 4:57 ` Dave Horsfall
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='CABH=_VQBS9hT-Y+7-u-VPM1pZVTuLxUr005WsGh6qP9hyH97-Q@mail.gmail.com' \
--to=paul.winalski@gmail.com \
--cc=ron@ronnatalie.com \
--cc=segaloco@protonmail.com \
--cc=tuhs@tuhs.org \
/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).