From: Stephen Clark <sclark46@earthlink.net>
To: tuhs@tuhs.org
Subject: Re: [TUHS] The Elements Of Style: UNIX As Literature
Date: Fri, 6 Nov 2020 11:46:08 -0500 [thread overview]
Message-ID: <e2b11bab-d0f4-8ef9-2949-764883431baa@earthlink.net> (raw)
In-Reply-To: <202011061519.0A6FJOAx034308@elf.torek.net>
On 11/6/20 10:19 AM, Chris Torek wrote:
>>> I think you're jumping to conclusions. The importance of 80
>>> characters (for small values of 80) is that it's a comfortable text
>>> width for human eyes.
>> Exactly this.
> Yes -- this is the (or at least "an") argument for two-column text
> on wide (8.5x11 or A4, or larger) paper pages.
>
>> It's also why I'm fine with smaller screens, I tried the giant apple
>> displays and found that those required head movement along with eye
>> movement.
>> I'm lazy.
> I am too, but I still use a big screen: I just fit a lot of
> smaller windows in it. I'd like to have a literal wall screen,
> especially if I'm in an interior, windowless (as in physical glass
> windows) room, so that part of the wall could be a "window"
> showing a view "outside" (real time, or the ocean, or whatever)
> and other parts of the wall could be the text I'm working on/with,
> etc.
>
> (But I'll make do with these 27" 4k displays. :-) )
>
> Chris
Could the 72 characters come from the original terminal ASR 33 Teletype?
The Model 33 printed on 8.5-inch (220 mm) wide paper, supplied on continuous
5-inch (130 mm) diameter rolls and fed via friction (instead of, e.g., tractor
feed). It printed at a fixed 10 characters per inch, and supported 74-character
lines,[13] although 72 characters is often commonly stated.
--
next prev parent reply other threads:[~2020-11-06 23:43 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 [this message]
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=e2b11bab-d0f4-8ef9-2949-764883431baa@earthlink.net \
--to=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).