The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] The Elements Of Style: UNIX As Literature
Date: Fri, 6 Nov 2020 09:40:52 -0600	[thread overview]
Message-ID: <175409f6-af94-601e-3db3-a5af5d7f64d0@gmail.com> (raw)
In-Reply-To: <CAC20D2PPw3Ua3-VpMYjh=NaC09=9Q528kqEvE7SvmO3Ly2JO0A@mail.gmail.com>

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

Clem,

It figures. I should have known there was a reason for the shorter lines 
other than display. Conventions are sticky and there appears to be a 
generation gap. I use single spaces between sentences, but my ancestors 
used 2... who knows why? :).

Will

On 11/6/20 9:07 AM, Clem Cole wrote:
> Will, I do still the same thing, but the reason for 72 for email being 
> that way is still card-based.  In FORTRAN the first column defines if 
> the card is new (a blank), a comment (a capital C), no zero a 
> 'continuation' of the last card.  But column 73-80 were 'special' and 
> used to store sequence #s (this was handy when you dropped your card 
> deck, card sorters could put it back into canonical order).  So 
> characters in those columns were typically ignored.   Thus when "Model 
> 28 ASR" (a.k.a. ASR-28) created it had 72 columns. It's interesting 
> that when its follow on the Model 33 was created, it actually had 74, 
> but most SW configured it to 72 [search for a manual on bit savers or 
> the like if you want the details].
>
> IIRC, the original DEC 'Glass TTY' - the VT-05 was 72, but later 
> terminals like the VT-52 were 80 columns, as was the ADM 3A.
>
> The one thing I will give the 'tyranny of 80-columns" is when I look 
> at code it starts to break that line size by a lot, I often think that 
> is a bell-weather of something that needs to be rewritten and 
> simplified, and/or the abstraction might not be right.   Like, 
> most/many rules there >>are<< often break exceptions, but when I do 
> look code with really long lines, I admit I am suspect.
>
>
> Clem
>
>
> On Fri, Nov 6, 2020 at 8:21 AM Will Senn <will.senn@gmail.com 
> <mailto:will.senn@gmail.com>> wrote:
>
>     On 11/6/20 12:34 AM, Rob Pike wrote:
>     >
>     https://github.com/golang/go/commit/a625b919163e76c391f2865d1f956c0f16d90f83
>     <https://github.com/golang/go/commit/a625b919163e76c391f2865d1f956c0f16d90f83>
>
>     >
>     <https://github.com/golang/go/commit/a625b919163e76c391f2865d1f956c0f16d90f83
>     <https://github.com/golang/go/commit/a625b919163e76c391f2865d1f956c0f16d90f83>>
>     Hilarious. I use fixed font - Monaco 14. But, 80 columns? not on your
>     life. I hate wrapped text output, if I can avoid it. That said, I
>     set my
>     soft word wrap in the text editor at 72 :). My convention comes from
>     early email though, not punched cards.
>
>     Will
>
>     -- 
>     GPG Fingerprint: 68F4 B3BD 1730 555A 4462  7D45 3EAA 5B6D A982 BAAF
>


-- 
GPG Fingerprint: 68F4 B3BD 1730 555A 4462  7D45 3EAA 5B6D A982 BAAF


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

  reply	other threads:[~2020-11-06 15:41 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 [this message]
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
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=175409f6-af94-601e-3db3-a5af5d7f64d0@gmail.com \
    --to=will.senn@gmail.com \
    --cc=clemc@ccc.com \
    --cc=tuhs@minnie.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).