public inbox for gentoo-pms@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gmail.com>
To: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
Cc: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] Fill column
Date: Tue, 19 Jan 2010 04:06:25 -0800	[thread overview]
Message-ID: <20100119120625.GB12986@hrair> (raw)
In-Reply-To: <82dd739f1001170626o343dfa75qc1fd64621f9645d7@mail.gmail.com>

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

On Sun, Jan 17, 2010 at 02:26:34PM +0000, Ciaran McCreesh wrote:
> 2010/1/17 Ulrich Mueller <ulm@gentoo.org>:
> >>>>>> On Sun, 17 Jan 2010, Ciaran McCreesh wrote:
> >> 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.
> >
> > Some people use several windows side by side, and the natural width of
> > these windows is 80 columns because almost all code adheres to it.
> 
> Almost all code does not adhere to it. 80 columns is a harmful legacy
> that needs to be abandoned now that we are no longer limited by 1970s
> terminals.

I'm not a particular fan of doing things just because of historical 
inertia.  That said, there are benefits to 80- namely, a shitload of 
source/text/etc is aimed at 80.  I'm not arrogant anything to claim 
"almost all code does not adhere to it"; I'll state the majority I 
work with on a day to day basis does however follow 80 w/ exemptions 
were appropriate.

Regardless, what works best for everyone is what should be used.  The 
'git blame' arguement would normally be valid, but in my opinion it's 
irrelevant in this case- it's a one time blip in tracing the source, 
further, the commit msgs used for PMS are of pretty varying quality 
thus decreasing the usefulness of blame.  Beyond that, blame is more 
of a source tool then text tool in terms of usefulness- I honestly 
can't think of the last time I had to do blame/annotate on PMS.

Either way, if the majority of folks find it easiest to work w/ an 80 
limit, go with 80.  I'd say the same if the magical number was 100 or 
unlimited.

Whatever makes it easiest for people to contribute and work on the 
document should win out- to be clear, I'm talking about the majority 
of folk not what best suits one person.

Personally, I prefer 80- if it'll help improve the source level 
reading of PMS and enough folks want it, I'm +1.  Barring that, +0.

~harring

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

  reply	other threads:[~2010-01-19 12:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2010-01-19 12:26     ` David Leverton
2010-02-01 10:18     ` [gentoo-pms] EXPORT_FUNCTIONS Ulrich Mueller
2010-02-05 20:21       ` [gentoo-pms] EXPORT_FUNCTIONS Ulrich Mueller
2010-02-05 21:22         ` David Leverton
  -- strict thread matches above, loose matches on Subject: below --
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
     [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

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=20100119120625.GB12986@hrair \
    --to=ferringb@gmail.com \
    --cc=ciaran.mccreesh@googlemail.com \
    --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