From mboxrd@z Thu Jan  1 00:00:00 1970
From: cym224@gmail.com (Nemo)
Date: Fri, 10 Nov 2017 11:18:28 -0500
Subject: [TUHS] 80 columns ...
In-Reply-To: <025501d3598f$008f19d0$01ad4d70$@ronnatalie.com>
References: <CAP6exYK_XOF16T-=h1ebmn3UsoXX5cHBkkiUvsGxJKxuHHa=fw@mail.gmail.com>
 <7wpo8rud7y.fsf@junk.nocrew.org>
 <60C45CFF-0B5C-4DAB-8936-BA27ECFFA487@gmail.com>
 <025501d3598f$008f19d0$01ad4d70$@ronnatalie.com>
Message-ID: <CAJfiPzz5ujn0Me-brHXrzMTumOxrDas6hE43bTQPuvJaEneY1g@mail.gmail.com>

On 9 November 2017 at 14:14, Ron Natalie <ron at ronnatalie.com> wrote:
> At least it’s not python where the indenting makes a semantic difference.

And for that reason, I have never used Python.  (I have a mental block
about that.)

As an 80-column aside, my alma mater allowed free runs in PL/C
(remember that?) on card decks.  I always numbered my cards in columns
73+ (and that save me from my clumsiness more than once).  One day,
they decided to read in all 80 columns.  Easily fixed by programming a
card-punch to add /* and */ but highly annoying.  But using cards
probably baked 80 columns into my head.

N.