public inbox for gentoo-pms@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: Christian Faulhammer <fauli@gentoo.org>
Cc: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] Fill column
Date: Sun, 17 Jan 2010 09:50:41 +0000	[thread overview]
Message-ID: <82dd739f1001170150v47b8396buefaa892167fac4c7@mail.gmail.com> (raw)
In-Reply-To: <20100117103043.55776971@gentoo.org>

2010/1/17 Christian Faulhammer <fauli@gentoo.org>:
>> Oh heck no. There's no excuse for using 70 or 80 columns for source
>> code any more. My old laptop can fit 100 across the screen
>> comfortably, which is much cleaner to work with.
>
>  We don't talk about source code but continous text even if having some
> mark-up around.  And best readability for such text is around 60
> characters per line, languages with long words may have more.

And the *generated* text is wrapped that way, or however else we want
it to be. We're discussing the source code, however, which is a whole
other thing, and none of your readability studies for printed texts
are relevant for it.

>> This bikeshed does not need repainting bright pink with orange spots.
>
>  And you don't want us to argue about the colour, right?

I don't want you to go and break 'git blame' etc and screw around with
something that doesn't need changing, yes. The not-quite-arbitrary
decision of "what fits on my laptop screen" that was originally made
is equally as good as or better than any alternative.

-- 
Ciaran McCreesh



  reply	other threads:[~2010-01-17  9:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13 18:40 [gentoo-pms] Clarify line continuation in make.defaults Jacob Godserv
2010-01-13 21:01 ` Christian Faulhammer
2010-01-17  4:07   ` [gentoo-pms] Fill column (was: Re: Clarify line continuation in make.defaults) Ulrich Mueller
2010-01-17  8:47     ` Ciaran McCreesh
2010-01-17  9:30       ` [gentoo-pms] Fill column Christian Faulhammer
2010-01-17  9:50         ` Ciaran McCreesh [this message]
2010-01-17 10:01           ` Christian Faulhammer
     [not found]             ` <82dd739f1001170311o14aafd13n8a140fc4c9ab487@mail.gmail.com>
     [not found]               ` <20100117142956.125b2e18@gentoo.org>
2010-01-17 14:36                 ` Ciaran McCreesh
     [not found]                   ` <19283.12619.238117.318780@a1i15.kph.uni-mainz.de>
2010-01-17 17:53                     ` Ciaran McCreesh
     [not found]   ` <2e0007041001141034w25cea618r3a0119b748aa3362@mail.gmail.com>
2010-01-17 11:16     ` [gentoo-pms] Clarify line continuation in make.defaults Christian Faulhammer
  -- strict thread matches above, loose matches on Subject: below --
2010-01-17 12:39 [gentoo-pms] Fill column Ulrich Mueller
2010-01-17 14:26 ` Ciaran McCreesh
2010-01-19 12:06   ` Brian Harring
2010-01-19 12:26     ` David Leverton

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=82dd739f1001170150v47b8396buefaa892167fac4c7@mail.gmail.com \
    --to=ciaran.mccreesh@googlemail.com \
    --cc=fauli@gentoo.org \
    --cc=gentoo-pms@lists.gentoo.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