Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 13 Oct 2008 18:52:49 -0400
From:      Thomas Dickey <dickey@radix.net>
To:        Jeremy Chadwick <koitsu@freebsd.org>
Cc:        questions@freebsd.org, borish@gmx.de
Subject:   Re: Sysinstall colors
Message-ID:  <20081013225249.GA1151@saltmine.radix.net>
In-Reply-To: <20081013210929.GA28598@icarus.home.lan>
References:  <op.uirsg0uw853yip@thinkpad> <20081009190941.GA12014@icarus.home.lan> <op.uitmp9ab853yip@thinkpad> <20081010190028.GA40991@icarus.home.lan> <op.uizab8ue853yip@thinkpad> <20081013210929.GA28598@icarus.home.lan>

next in thread | previous in thread | raw e-mail | index | archive | help

--MGYHOYXEY6WxJCY8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Oct 13, 2008 at 02:09:29PM -0700, Jeremy Chadwick wrote:
> On Mon, Oct 13, 2008 at 09:42:04PM +0200, borish@gmx.de wrote:
> > After some trial and error, I put
> >
> > XTerm*color7:      #bebebe
> >
> > in my .Xdefaults. Now the yellow sysinstall font is much more legible =
=20
> > inside an xterm. This works for both xterm and rxvt. The rxvt man page =
=20
> > proved very useful.
> >
> > Now I have solved my problem but other users may experience the same =
=20
> > problem. Is it possible to modify sysinstall so that it uses a darker =
=20
> > background gray when run inside xterm?
>=20
> I'm not sure this is desirable or recommendable.  There are some
> terminal emulation programs -- specifically, PuTTY -- which emulate
> TERM=3Dxterm.  The RGB colours in PuTTY look just fine: quite legible.

more/less (putty's wrapping behavior differs)

> The key problem here is this: there are no more darker grey backgrounds
> available with the limited colour set available.  You get one grey bg --
> sequence \e[47m; -- and that's it.  If you want other colours, you have
> to have a 256-colour xterm compiled, which supports an extended palette,
> and there's no way to detect if someone has such a capable terminal
> (basing it on $TERM is not correct).

actually, basing it on $TERM is the way most people would do it,
e.g.,

xterm-256color|xterm with 256 colors,
	am, bce, ccc, km, mc5i, mir, msgr, npc, xenl,
	colors#256, cols#80, it#8, lines#24,
	acsc=3D``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,
=2E..
	initc=3D\E]4;%p1%d;rgb:%p2%{255}%*%{1000}%/%2.2X/%p3%{255}%*%{1000}%/%2.2X=
/%p4%{255}%*%{1000}%/%2.2X\E\\,
=2E..

--=20
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

--MGYHOYXEY6WxJCY8
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (SunOS)
Comment: For info see http://www.gnupg.org

iD8DBQFI89EytIqByHxlDocRArHfAJ92/OXgiOD4TCp3nVqF/21LN3YMYwCfSIlF
++awIzTOt0MyhpCibKTmJJ0=
=jmaY
-----END PGP SIGNATURE-----

--MGYHOYXEY6WxJCY8--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081013225249.GA1151>