Date: Wed, 5 Nov 2003 00:32:48 +0100 From: Erik Trulsson <ertr1013@student.uu.se> To: Darryl Okahata <darrylo@soco.agilent.com> Cc: freebsd-stable@freebsd.org Subject: Re: Serious (ha-ha) bug in 4.9-RELEASE Message-ID: <20031104233248.GB34632@falcon.midgard.homeip.net> In-Reply-To: <200311041750.JAA20518@mina.soco.agilent.com> References: <Pine.GSO.4.10.10311041137170.2711-100000@pcnet5.pcnet.com> <200311041750.JAA20518@mina.soco.agilent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 04, 2003 at 09:50:28AM -0800, Darryl Okahata wrote: > Daniel Eischen <eischen@vigrid.com> wrote: > > > > Very critical indeed... And with such a huge userbase that it took six > > > months before anybody noticed this problem. :-) > > > > No, we noticed it here at work where we use Sun Solaris > > boxes as our development systems. I didn't know what the > > problem was until now. It is very very annoying to have > > man, more, less, etc, screw up your display when using > > them while remotely logged in to our FreeBSD boxes. > > Oh, so THAT's the cause. I've been seeing this for quite a while, > but haven't been sufficiently annoyed to track it down. I just assumed > that either termcap or xterm was broken. I've just been using > "TERM=vt100" as a kludgearound. Neither is broken. It is just that the termcap entry for xterm that you use does not correspond to the xterm you are running. Very annoying, but not really any single component which is broken. > > > The > > symptoms are that everything gets highlighted and underlined > > and it stays that way forcing you to close the xterm and > > open another. > > An easier fix is to run vi and exit, which resets the > highlighting. Doing a 'tput reset' should also do the trick. -- <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031104233248.GB34632>