mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: } <grundig@teleline.es>
Cc: kay.sievers@vrfy.org, linux-kernel@vger.kernel.org
Subject: Re: 80 column line limit?
Date: Thu, 5 Jan 2006 23:27:23 +0100	[thread overview]
Message-ID: <9a8748490601051427x1ab06565o2e7b76a28f2b42fc@mail.gmail.com> (raw)
In-Reply-To: <20060105154330.da1016fc.grundig@teleline.es>

On 1/5/06, }\x02 <grundig@teleline.es> wrote:
> El Thu, 5 Jan 2006 14:27:23 +0100,
> Jesper Juhl <jesper.juhl@gmail.com> escribió:
>
> > I very often work in console (or xterm) and editing kernel code. Files
> > with lines >80 col. are quite annoying to have to scroll left/right in
>
> I wonder why (we) people keeps working (and writing emails) with a 80
> cols limit - monitors are BIG these days and even the crappiest
> graphic card can do better than 80x25 even without using fbcon. Is not

I'm well aware that my hardware can easily do more than 80 columns,
but that's simply not as pleasant to read. Even in X I usually keep my
xterms to 80 columns and with a resonably large font so I don't have
to strain my eyes too much when reading.

> that breaking the 80-cols rules is annoying, working with such setups
> are painful even to run basic shell scripts. These days hardware can do
> better things than 80-col consoles even for console users.
>
It's not about hardware capabilities, it's about readability.

--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  parent reply	other threads:[~2006-01-05 22:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-05 13:02 Kay Sievers
2006-01-05 13:27 ` Jesper Juhl
     [not found]   ` <20060105154330.da1016fc.grundig@teleline.es>
2006-01-05 22:27     ` Jesper Juhl [this message]
2006-01-05 13:32 ` Pekka Enberg
2006-01-05 21:14   ` Kay Sievers
2006-01-05 22:03     ` Jan Engelhardt
2006-01-06  5:52       ` Willy Tarreau
2006-01-06  7:09         ` Jan Engelhardt
2006-01-05 13:43 ` Giuliano Pochini
2006-01-05 23:02 ` Alistair John Strachan
2006-01-06  1:34 ` Jim Nance
2006-01-06  7:12   ` Jan Engelhardt
     [not found] <5rD2D-xs-11@gated-at.bofh.it>
2006-01-05 18:08 ` Bodo Eggert
2006-01-06  7:14   ` Jan Engelhardt

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=9a8748490601051427x1ab06565o2e7b76a28f2b42fc@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=grundig@teleline.es \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®