From: James Ingham <jingham@cygnus.com>
To: Moses DeJong <dejong@cs.umn.edu>
Cc: James Ingham <jingham@cygnus.com>, insight@sourceware.cygnus.com
Subject: Re: A font size patch for large screens.
Date: Wed, 11 Aug 1999 11:55:00 -0000 [thread overview]
Message-ID: <14257.51069.531162.960957@leda.cygnus.com> (raw)
In-Reply-To: <Pine.GSO.4.05.9908111320180.23318-100000@brin.cs.umn.edu>
Moses,
>
> A buddy of mine has a PowerBook, those are sweet machines. Only problem
> is they get to hot for my lap (yee-ouch).
Yeah, this was true for a while. They did something slick in the OS
going from 8.5 to 8.6 to reduce power consumption and temperature.
The PowerBook running MacOS 8.6 is pretty comfortable, though it was a
bit toasty under 8.5. If you are running LinuxPPC, you had better
just put it on a table...
The newer Bronze ones are supposedly lots cooler.
>
> Yeah, font sizes are always a pain. A size of 16 looks great on my
> Linux box but is it flat out wrong on other systems. As long as
> the default is "close", thats all I care about. The current default
> of 9 is unreadable on my system.
>
> > Thanks for the patch. The idea is great, but I don't think the
> > algorithm is quite right, however. I think the laptop case is an
> > extreme example of many pixels + small physical size. I have a Sun
> > display at 1280x1024, and 16 is way too big a font for the default.
> > 14 is okay, though a bit on the biggish side, 11 is really pretty
> > good, though 9 is definately too small.
>
> Change away. I would love to test out any new algo.
>
Okay, I'll fool around with this when I get half a mo', I am pretty
busy right now.
Jim
next prev parent reply other threads:[~1999-08-11 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-11 2:18 Moses DeJong
1999-08-11 10:36 ` James Ingham
1999-08-11 11:27 ` Moses DeJong
1999-08-11 11:55 ` James Ingham [this message]
1999-08-11 11:56 ` James Ingham
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=14257.51069.531162.960957@leda.cygnus.com \
--to=jingham@cygnus.com \
--cc=dejong@cs.umn.edu \
--cc=insight@sourceware.cygnus.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).