The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: John Cowan <cowan@ccil.org>
To: sclark46@earthlink.net
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] The Elements Of Style: UNIX As Literature
Date: Fri, 6 Nov 2020 13:24:14 -0500	[thread overview]
Message-ID: <CAD2gp_QD4bucOopm5U8+KtRcV=yA=8=CByy7h7cn89J=on+Gzg@mail.gmail.com> (raw)
In-Reply-To: <3c54b19d-e604-68eb-2b4b-0b65e9cfb896@earthlink.net>

[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]

On Fri, Nov 6, 2020 at 12:26 PM Stephen Clark <sclark46@earthlink.net>
wrote:


> May have had to do with the first terminal commonly used with UNIX.
>
> The Model 33
>

In fact the Labs had the more recent Model 37, which did lower case, unlike
the 33.  Consequently, Unix was (I think) the first case-sensitive
operating system.  However, it had to work on 33s as well; if you tried to
log in using an uppercase username, login would turn on the IUCLC and OLCUC
bits of /dev/tty, and if you needed an uppercase letter you had to escape
it (I think with \), which the tty driver processed.

Thanks to everyone for filling in all the gaps in the chain from dollar
bills to 80-column terminal windows that I had left implicit.  To clarify
my position, what I am opposed to is not the use of 80-column windows for
*reading* email.  I'm not happy with what happens to text that is
hard-wrapped at 80 columns when displayed in a narrower window, as often
happens to me now that I use larger fonts than I used to.  The
text/format-flowed MIME type was supposed to help with this problem, but
never really caught on.



"Well, I'm back."  --Sam        John Cowan <cowan@ccil.org>

[-- Attachment #2: Type: text/html, Size: 2520 bytes --]

  reply	other threads:[~2020-11-06 18:25 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05 22:10 Tyler Adams
2020-11-06  0:39 ` Kevin Bowling
2020-11-06  1:41 ` Larry McVoy
2020-11-06  5:04   ` John Cowan
2020-11-06  5:16     ` Steve Nickolas
2020-11-06  6:34     ` Rob Pike
2020-11-06 13:20       ` Will Senn
2020-11-06 15:07         ` Clem Cole
2020-11-06 15:40           ` Will Senn
2020-11-06 15:46             ` Chris Torek
2020-11-06 22:54               ` Greg 'groggy' Lehey
2020-11-06 23:29                 ` Steffen Nurpmeso
2020-11-06 22:31           ` Dave Horsfall
2020-11-06 23:41             ` Warren Toomey
2020-11-06  6:37     ` Greg 'groggy' Lehey
2020-11-06 15:06       ` Larry McVoy
2020-11-06 15:18         ` Bakul Shah
2020-11-06 15:19         ` Chris Torek
2020-11-06 16:46           ` Stephen Clark
2020-11-06 18:51         ` Jon Steinhart
2020-11-06 22:09           ` John Cowan
2020-11-06 22:44             ` Jon Steinhart
2020-11-06 22:12         ` Andy Kosela
2020-11-06 22:23           ` Larry McVoy
2020-11-07  0:16             ` Dave Horsfall
2020-11-08 23:23               ` George Michaelson
2020-11-06 17:05       ` Paul Winalski
2020-11-06 17:07         ` Larry McVoy
2020-11-06 17:25           ` Warner Losh
2020-11-06 17:13       ` Adam Thornton
2020-11-06 17:26         ` Stephen Clark
2020-11-06 18:24           ` John Cowan [this message]
2020-11-06 21:10   ` 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='CAD2gp_QD4bucOopm5U8+KtRcV=yA=8=CByy7h7cn89J=on+Gzg@mail.gmail.com' \
    --to=cowan@ccil.org \
    --cc=sclark46@earthlink.net \
    --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).