public inbox for gentoo-pms@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christian Faulhammer <fauli@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] Fill column
Date: Sun, 17 Jan 2010 11:01:04 +0100	[thread overview]
Message-ID: <20100117110104.0b593d33@gentoo.org> (raw)
In-Reply-To: <82dd739f1001170150v47b8396buefaa892167fac4c7@mail.gmail.com>

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

Hi,

Ciaran McCreesh <ciaran.mccreesh@googlemail.com>:
> 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.

 But usually I read diffs on the screen and seldomly read PMS in
formatted text, so not my readability studies but scientific facts
apply here as well.

> 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.

 git blame is an argument, right.  The line wrapping goes on my nerve
for quite some time but I postponed any complaints until some real work
is done.

V-Li


-- 
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode

<URL:http://gentoo.faulhammer.org/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-01-17 10:01 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
2010-01-17 10:01           ` Christian Faulhammer [this message]
     [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=20100117110104.0b593d33@gentoo.org \
    --to=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