The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: steffen@sdaoden.eu (Steffen Nurpmeso)
Subject: [TUHS] 80 columns ...
Date: Thu, 09 Nov 2017 00:46:52 +0100	[thread overview]
Message-ID: <20171108234652.SM0h5%steffen@sdaoden.eu> (raw)
In-Reply-To: <CAEoi9W7F7Lb_V0dMwu2-cYakRs7yP5msT4=sD-Btw0TNcS5vvg@mail.gmail.com>

Dan Cross <crossd at gmail.com> wrote:
 |On Wed, Nov 8, 2017 at 4:02 PM, Larry McVoy <lm at mcvoy.com> wrote:
 |> On Wed, Nov 08, 2017 at 08:52:03PM +0000, ron minnich wrote:
 |>> So, 80 column folks, would you find this
 |>> a(b,
 |>> c,
 |>> d)
 |>>
 |>> more readable than
 |>> a(b,c,d)

Someone who is no longer on this list said to the same topic to
me, in October:

  Wer zu schnell nach Rechts kommt, strukturiert zu wenig ;-)

  Who approaches the right too fast, does not structure enough

More or less.  In the context that i turned to space indentation
when i started using C not C++.

 |> yeah, I do.  I work on thinkpad x220 sized machines which are just \
 |> big enough
 |> for two 80 column windows with a little left over.  When I'm checking \
 |> in code,
 |> reviewing code, debugging code, I frequently want to see two versions \
 |> of the
 |> same file side by side.  If you code wider than 80 columns it greatly \
 |> reduces
 |> the speed at which you can figure out what happened.

I missed the possibility in screen(1), now in tmux(1) i can use

  bind-key -T prefix       <      set-window-option force-width 80
  bind-key -T prefix       >      set-window-option force-width 0

again.

 |The thing that sort of vexes me about these arguments is that the
 |number 80 is so arbitrary. If you can fit two 80 column windows
 |side-by-side, then surely you could do the same with two 78-, 72- or
 |even 64-column windows. So why not 64, 72 or 78 columns?

Whatever you say, i only wanted to add that "Human attention" is
only so far stretchable, and that readers likely cannot grasp line
lengths of that size, especially if densely packed or the
surrounding lines are of significantly different length.  Some
neurologist could surely correct me.
With tab indentation, a function with one level of conditionals
eats up 16 rows, so the more or less ideal line length of 64 (if
i recall correctly Knuth advocated 66) is the result.

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)


  parent reply	other threads:[~2017-11-08 23:46 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 20:52 ron minnich
2017-11-08 21:02 ` Larry McVoy
2017-11-08 21:19   ` Dan Cross
2017-11-08 21:24     ` Larry McVoy
2017-11-08 21:28       ` Steve Nickolas
2017-11-08 21:48         ` [TUHS] (cassette) tape coming back [was " Charles H Sauer
2017-11-08 22:46           ` Don Hopkins
2017-11-08 23:28         ` [TUHS] " Dave Horsfall
2017-11-08 23:35           ` Ron Natalie
2017-11-08 23:39             ` Dave Horsfall
2017-11-08 21:34       ` Dan Cross
2017-11-08 21:40         ` Dan Cross
2017-11-08 21:40         ` Larry McVoy
2017-11-08 21:43           ` Dan Cross
2017-11-09  1:00             ` Theodore Ts'o
2017-11-08 23:46     ` Steffen Nurpmeso [this message]
2017-11-09  6:52       ` Otto Moerbeek
2017-11-08 21:06 ` Bakul Shah
2017-11-08 21:18   ` Steve Nickolas
2017-11-08 22:17 ` Grant Taylor
2017-11-08 22:30   ` Arthur Krewat
2017-11-08 23:07     ` Andy Kosela
2017-11-08 23:15       ` Arthur Krewat
2017-11-08 23:15         ` Warner Losh
2017-11-08 23:49           ` Arthur Krewat
2017-11-09  0:04             ` Dave Horsfall
2017-11-08 23:24         ` Andy Kosela
2017-11-09  7:24 ` Lars Brinkhoff
2017-11-09 15:02   ` Don Hopkins
2017-11-09 19:14     ` Ron Natalie
2017-11-10 16:18       ` Nemo
2017-11-10 19:05         ` Jon Steinhart
2017-11-10 20:36           ` Toby Thain
2017-11-10 20:39             ` Larry McVoy
2017-11-10 20:46               ` Warner Losh
2017-11-10 20:59                 ` Larry McVoy
2017-11-11  9:24                 ` David Arnold
2017-11-10 20:43             ` Jon Steinhart
2017-11-10 20:58               ` Larry McVoy
2017-11-10 21:02                 ` Jon Steinhart
2017-11-10 21:09                   ` Larry McVoy
2017-11-10 21:12                     ` Jon Steinhart
2017-11-10 21:34                       ` William Corcoran
2017-11-10 21:50                         ` Jon Steinhart
2017-11-10 22:58                         ` Dave Horsfall
2017-11-10 23:05                           ` Jon Steinhart
2017-11-10 23:52                             ` Toby Thain
2017-11-11  0:24                             ` Larry McVoy
2017-11-11 16:40                   ` Ian Zimmerman
2017-11-11 16:47                     ` Larry McVoy
2017-11-11 17:23                       ` Jon Steinhart
2017-11-11 17:38                         ` Ralph Corderoy
2017-11-10 22:46               ` Toby Thain
2017-11-10 22:59                 ` Jon Steinhart
2017-11-11 14:33                   ` Andy Kosela
2017-11-11 17:19                     ` Jon Steinhart
2017-11-11 17:24                       ` Larry McVoy
2017-11-11 17:25                         ` Jon Steinhart
2017-11-10 23:59           ` Don Hopkins
2017-11-10 22:10         ` Dave Horsfall
2017-11-09 20:46     ` Lars Brinkhoff
2017-11-10 17:21 Norman Wilson
2017-11-10 17:56 ` Larry McVoy
2017-11-11 17:04 ` Ian Zimmerman
2017-11-11 17:30   ` Random832
2017-11-11 18:05     ` Ian Zimmerman

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=20171108234652.SM0h5%steffen@sdaoden.eu \
    --to=steffen@sdaoden.eu \
    /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).