From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: ridiculously wide handbook pages
Date: Thu, 30 Sep 2010 20:55:45 +0000 (UTC) [thread overview]
Message-ID: <i82tgh$67m$1@dough.gmane.org> (raw)
In-Reply-To: i82s8v$v4b$1@dough.gmane.org
On 2010-09-30, J??rg Schaible <joerg.schaible@gmx.de> wrote:
>> I could reduce the minimum size of my "fixed" font, but that only
>> helps until the next web page comes along with an even wider code
>> block.
>
> Try a different fixed font. At the end I've chosen "Monotype",
> because it seems to have the narrowest well-readable letters.
That's still just a kludge/bandage for a broken document.
I've got no complaint about the width of the listing blocks.
The problem is that the wrap width of normal text paragraphs shouldn't
be determined by the width of listing blocks. It should be determined
by the width of the browser window.
I'd also set a maximum text width to keep paragraphs somewhat readable
when you widen the window to see all of a really wide listing block.
But, I'm willing to admit that's a more of a style/preference
question.
Here's an example of how to do it right (both decoupled text/listing
widths and a max-width for text):
http://www.panix.com/~grante/wrapdemo.html
I've filed a bug, so anybody with an opinion can weigh in there as
well.
--
Grant Edwards grant.b.edwards Yow! Everybody gets free
at BORSCHT!
gmail.com
next prev parent reply other threads:[~2010-09-30 20:56 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 ` [gentoo-user] " Darren Kirby
2010-09-30 18:18 ` [gentoo-user] " 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 [this message]
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='i82tgh$67m$1@dough.gmane.org' \
--to=grant.b.edwards@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