public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Darren Kirby <bulliver@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ridiculously wide handbook pages
Date: Thu, 30 Sep 2010 11:59:38 -0600	[thread overview]
Message-ID: <AANLkTinMZEyXMdP743AbQ2EZ3gpaR2F9VHXvgVT7tD+Q@mail.gmail.com> (raw)
In-Reply-To: <i82gfj$4sk$1@dough.gmane.org>

On Thu, Sep 30, 2010 at 11:13 AM, Grant Edwards
<grant.b.edwards@gmail.com> wrote:

>
> I can understand that things like example code blocks or sample
> command input/output blocks might need to be wide enough to require
> horizontal scrolling of a browser window, but normal text paragraphs
> with 160 characters per line?

I'm not seeing a problem here. Sure, the lines are long but my screen
is large and my resolution is high. A quick play with firefox and konq
shows that the text reformats itself quite elegantly when you resize
your browser window to say, 2/3 of screen width. I think that's a
better solution than imposing some arbitrary line length on everyone
no matter their screen size and resolution.

D
--
Support the mob or mysteriously disappear...
I'm on flickr: http://www.flickr.com/photos/badcomputer/



  parent reply	other threads:[~2010-09-30 17:59 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30 17:13 [gentoo-user] ridiculously wide handbook pages Grant Edwards
2010-09-30 17:26 ` Volker Armin Hemmann
2010-09-30 17:57   ` [gentoo-user] " Grant Edwards
2010-09-30 17:59 ` Darren Kirby [this message]
2010-09-30 18:18   ` Grant Edwards
2010-09-30 18:31     ` Darren Kirby
2010-09-30 18:36       ` Grant Edwards
2010-09-30 18:55         ` Darren Kirby
2010-09-30 19:23           ` Grant Edwards
2010-09-30 20:34             ` Jörg Schaible
2010-09-30 20:55               ` Grant Edwards
2010-09-30 21:13               ` Grant Edwards
2010-09-30 18:35     ` Grant Edwards
2010-09-30 18:39     ` Dale
2010-09-30 18:50       ` Grant Edwards
2010-09-30 19:14         ` Dale
2010-09-30 19:42           ` Grant Edwards
2010-09-30 19:50             ` Dale
2010-09-30 20:05               ` Grant Edwards
2010-09-30 20:41                 ` Dale
2010-09-30 18:11 ` [gentoo-user] " Al
2010-09-30 18:19   ` [gentoo-user] " Grant Edwards
2010-09-30 18:23 ` Nikos Chantziaras
2010-09-30 18:34 ` [gentoo-user] " Mark Knecht
2010-09-30 18:39   ` Darren Kirby
2010-09-30 18:49     ` [gentoo-user] " Grant Edwards
2010-09-30 18:39   ` Grant Edwards
2010-09-30 22:53 ` [gentoo-user] " Jacob Todd
2010-09-30 23:15   ` [gentoo-user] " Grant Edwards
2010-09-30 23:18     ` Jacob Todd
2010-10-01  0:27       ` Dale
2010-10-01  0:59         ` Jacob Todd
2010-10-01 22:18 ` [gentoo-user] " Renat Golubchyk
2010-10-02  2:16   ` Stroller
2010-10-02  9:06     ` Renat Golubchyk
2010-10-03 17:32       ` Peter Humphrey
2010-10-04  2:00         ` Renat Golubchyk
2010-10-04  6:24           ` Mick
2010-10-04 10:20           ` Peter Humphrey
2010-10-02  3:21   ` [gentoo-user] " Grant Edwards
2010-10-04 17:06   ` [gentoo-user] " Fatih Tümen
2010-10-04 18:24     ` [gentoo-user] " Grant Edwards
2010-10-04 18:27     ` [gentoo-user] " Derek Tracy
2010-10-04 19:20       ` Fatih Tümen

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=AANLkTinMZEyXMdP743AbQ2EZ3gpaR2F9VHXvgVT7tD+Q@mail.gmail.com \
    --to=bulliver@gmail.com \
    --cc=gentoo-user@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