--tThc/1wpZn/ma/RB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Apr 25, 2007 at 02:21:49PM -0400, George Georgalis wrote:
> On Thu, Oct 05, 2006 at 12:20:00PM -0400, Thomas Dickey wrote:
> >On Thu, Oct 05, 2006 at 11:30:02AM -0400, George Georgalis wrote:
> >> While I see the logic that the client xterm/termcap is very
> >> important, I cannot make any sense as to why my amd64 host
> >> is having problems while the i386 does not. If anyone could
> >> elucidate that, I am very curious.
=2E..

> Much appreciated! So if "e)" is the problem... is
> it a problem with screen or termcap?  Sounds like

I had the impression that NetBSD's termcap library was designed to make
things transparent - so that unless an application inspects the buffer
returned by tgetent(), there would be no problem seen by an application.

It's a nuisance for screen to set its TERMCAP variable so large - that's
arguably a bug in screen.  It can break applications that use that
variable.  Presumably NetBSD's termcap library does the right thing
for applications that get their termcap data via this source...

> screen but I'm not sure? Do other applications have
> this problem? Would setting TERM within screenrc
> be of any help. (of course we need color)
>=20
> I did an amd64 3.1 cdrom install, built colorls and
> screen from pkgsrc, got the toor account setup in
> its own dir, so the only non-standard rc file or env
> is pkgsrc in PATH.
>=20
> On local console, "colorls -G /" works unless within
> screen, which generates OOPS in place of color
> codes.
>=20
> Can this PR be revisited? Is there any more info I
> can provide? (I'd like to report what netbsd-4 does,
> but I've not been able to get the upgrade to go.)

hmm - bear in mind that I'm not the NetBSD termcap maintainer - I maintain
xterm and ncurses and am offering advice...

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

--tThc/1wpZn/ma/RB
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

iD8DBQFGL7+qtIqByHxlDocRAgmEAJ9vLtO8oolSD9lbOWo5Gv3ASF+12gCcDuld
czDG0/C5bRjE4ErkcKqn9bY=
=sw2X
-----END PGP SIGNATURE-----

--tThc/1wpZn/ma/RB--