Date: Sat, 28 Jul 2007 23:50:07 -0400 (EDT)
From: Daniel Eischen <deischen@freebsd.org>
To: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
Cc: current@freebsd.org
Subject: Re: TERM={xterm-r5,xterm-r6} behaving badly with man(1)
Message-ID: <Pine.GSO.4.64.0707282347310.24233@sea.ntplx.net>
In-Reply-To: <86vec4dxcy.fsf@ds4.des.no>
References: <Pine.GSO.4.64.0707281007310.21300@sea.ntplx.net> <86vec4dxcy.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-1804928587-1185681007=:24233 Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Sat, 28 Jul 2007, Dag-Erling Sm=C3=B8rgrav wrote: > 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=3Dxter= m-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. Well, something did change recently to get this behavior. And why do we have a termcap xterm entry that doesn't exhibit this behavior? --=20 DE ---559023410-1804928587-1185681007=:24233--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0707282347310.24233>