public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Hazelton <dhazelton@enter.net>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	akpm@osdl.org, linux-kernel@vger.kernel.org, jeff@garzik.org
Subject: Re: [PATCH] intel-rng: Undo mess made by an 80 column extremist
Date: Thu, 7 Jun 2007 19:01:28 -0400	[thread overview]
Message-ID: <200706071901.28560.dhazelton@enter.net> (raw)
In-Reply-To: <m3d507z8zq.fsf@maximus.localdomain>

On Thursday 07 June 2007 18:37:45 Krzysztof Halasa wrote:
> Daniel Hazelton <dhazelton@enter.net> writes:
> > Why? My consoles are *all* still 80x24 text mode. It's only if I decide
> > to monkey with the settings (and why fix what isn't broken?) or when I'm
> > in X that I get a bigger screen than that.
> >
> > I think the general consensus on the 80 character lines isn't for the
> > average home user, but for the people that have things like old Wyse
> > terminals and such hooked up.
>
> Of course! But I don't write code using the system console nor old
> Wyse etc. serial terminal and I suspect (almost?) nobody does that.
>
> Do you?

No, I don't use a Wyse terminal, but I do a lot of my coding without X 
running. I don't know why, but it might be because I can then take off my 
glasses and not have to worry about the characters getting too blurred to 
read.


DRH

> Number of characters printed by the kernel (printk()) - sure, still
> 80 chars to suid everybody (and yes, printk messages show up on system
> consoles).



  reply	other threads:[~2007-06-07 23:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07 15:22 [PATCH] intel-rng: Undo mess made by an 80 column extremist Alan Cox
2007-06-07 15:23 ` Jeff Garzik
2007-06-07 15:44   ` Alan Cox
2007-06-07 17:22     ` Jeff Garzik
2007-06-07 21:17 ` Krzysztof Halasa
2007-06-07 21:32   ` Alistair John Strachan
2007-06-07 22:06     ` Krzysztof Halasa
2007-06-08  1:08       ` H. Peter Anvin
2007-06-08  1:25         ` Jeff Garzik
2007-06-08 10:11           ` Peter Zijlstra
2007-06-09 20:33             ` Krzysztof Halasa
2007-06-07 22:32   ` Daniel Hazelton
2007-06-07 22:37     ` Krzysztof Halasa
2007-06-07 23:01       ` Daniel Hazelton [this message]
2007-06-07 22:46     ` Jesper Juhl
2007-06-07 23:04       ` Daniel Hazelton
2007-06-08  1:44   ` John Stoffel
2007-06-08  1:47     ` Jeff Garzik
2007-06-08  1:56       ` John Stoffel
2007-06-08  2:07         ` Jeff Garzik
2007-06-08  2:11           ` John Stoffel
2007-06-08 18:21             ` Ingo Oeser
2007-06-09 20:41         ` Krzysztof Halasa

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=200706071901.28560.dhazelton@enter.net \
    --to=dhazelton@enter.net \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=khc@pm.waw.pl \
    --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