From owner-freebsd-stable@FreeBSD.ORG Tue Nov 4 15:32:52 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 964A316A4CF for ; Tue, 4 Nov 2003 15:32:52 -0800 (PST) Received: from falcon.midgard.homeip.net (h76n3fls24o1048.bredband.comhem.se [213.67.148.76]) by mx1.FreeBSD.org (Postfix) with SMTP id 4B54D43FCB for ; Tue, 4 Nov 2003 15:32:49 -0800 (PST) (envelope-from ertr1013@student.uu.se) Received: (qmail 34739 invoked by uid 1001); 4 Nov 2003 23:32:48 -0000 Date: Wed, 5 Nov 2003 00:32:48 +0100 From: Erik Trulsson To: Darryl Okahata Message-ID: <20031104233248.GB34632@falcon.midgard.homeip.net> Mail-Followup-To: Darryl Okahata , deischen@freebsd.org, freebsd-stable@freebsd.org References: <200311041750.JAA20518@mina.soco.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200311041750.JAA20518@mina.soco.agilent.com> User-Agent: Mutt/1.5.4i cc: deischen@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: Serious (ha-ha) bug in 4.9-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2003 23:32:52 -0000 On Tue, Nov 04, 2003 at 09:50:28AM -0800, Darryl Okahata wrote: > Daniel Eischen 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. -- Erik Trulsson ertr1013@student.uu.se