Date: Sat, 28 Jul 2007 23:36:29 +0200
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To: deischen@freebsd.org
Cc: current@freebsd.org
Subject: Re: TERM={xterm-r5,xterm-r6} behaving badly with man(1)
Message-ID: <86vec4dxcy.fsf@ds4.des.no>
In-Reply-To: <Pine.GSO.4.64.0707281007310.21300@sea.ntplx.net> (Daniel Eischen's message of "Sat\, 28 Jul 2007 10\:19\:04 -0400 \(EDT\)")
References: <Pine.GSO.4.64.0707281007310.21300@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Daniel Eischen <eischen@vigrid.com> writes: > Sometime in the last few months, something changed (broke IMHO) when > using TERM=3Dxterm-r5 or TERM=3Dxterm-r6. I've been setting TERM=3Dxterm= -r5 > when logging in to my BSD boxes remotely from my Solaris boxes, so that > man(1) works. But after updating my relatively old (May?) -current > box, xterm-r5 and xterm-r6 no longer do the right thing when using > man. With TERM set to either one of those, man(1) will clear the > screen after it is done, leaving no trace of the man page behind. This is the *correct* behaviour. The termcap entry is supposed to reflect the capabilities of the terminal, not your personal preferences. If you don't like it, you can override it using the TERMCAP environment variable. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86vec4dxcy.fsf>