The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron@ronnatalie.com (Ron Natalie)
Subject: [TUHS] C question for the historians
Date: Wed, 8 Nov 2017 15:32:36 -0500	[thread overview]
Message-ID: <010c01d358d0$b6f110d0$24d33270$@ronnatalie.com> (raw)
In-Reply-To: <20171108202334.GA14526@mcvoy.com>

80 was the number of columns in the IBM punched cards.
Teletypes only had 72 coumns.
Most lineprinters could do 132.

I remember making the jump from the Visual200's (a vt52 clone) to the 5620
DMD.   I actually had at home in my kitchen a ASR-37.    It was one of the
only terminals I have used that I didn't need to engage nl mode.
It had a big NEWLINE key that sent "\n" and didn't need to have the "\r"
also sent.    It also did stuff with all the SI/SO and ESC 8 and 9 things
that nroff sent by default without the need for an converting filter.

Amusingly, it was also one of the the only terminals I used that did
something with CD and DSR.    Upon DSR coming up, it would turn on the motor
and on CD a giant green PROCEED indicator came on.    I never turned it off,
I just shutdown the modem.

-----Original Message-----
From: TUHS [mailto:tuhs-bounces@minnie.tuhs.org] On Behalf Of Larry McVoy
Sent: Wednesday, November 8, 2017 3:24 PM
To: ron minnich
Cc: tuhs at minnie.tuhs.org
Subject: Re: [TUHS] C question for the historians

> For me one of the worst is the 80-column requirement that came from 
> out of I don't know where. Let's see, we're all getting 4k monitors, 
> and yet somehow
> 80 columns is how we have to write code? Hollerith would be proud.

I'm an 80 column person, I like it for side by side diffs, stuff like that.
I also read very very fast by reading down the center and using peripheral
vision for either side (hockey habits die hard).  I can't do that with much
wider than 80 column.

I had a guy working for me who started to argue with me and caught himself:
"I work for you, so it's 80 columns.  When you work for me it won't be."

Fair enough.



  reply	other threads:[~2017-11-08 20:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 16:17 Arthur Krewat
2017-11-08 16:27 ` Warner Losh
2017-11-09 10:17   ` Michael Kjörling
2017-11-08 18:14 ` Ralph Corderoy
2017-11-08 18:34   ` Arthur Krewat
2017-11-08 19:05   ` Larry McVoy
2017-11-08 20:13     ` ron minnich
2017-11-08 20:23       ` Larry McVoy
2017-11-08 20:32         ` Ron Natalie [this message]
2017-11-08 20:39       ` Warner Losh
2017-11-08 20:41       ` Chet Ramey
2017-11-09  1:22         ` Ralph Corderoy
2017-11-09  1:41           ` Chet Ramey
2017-11-09  1:49             ` Arthur Krewat
2017-11-08 20:43       ` Bakul Shah
2017-11-08 20:55       ` Steve Nickolas
2017-11-08 20:36     ` Warner Losh

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='010c01d358d0$b6f110d0$24d33270$@ronnatalie.com' \
    --to=ron@ronnatalie.com \
    /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).