From owner-freebsd-bugs  Thu Nov 18  2:33:38 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id B216E153C6; Thu, 18 Nov 1999 02:33:37 -0800 (PST)
	(envelope-from sheldonh@FreeBSD.org)
Received: (from sheldonh@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id CAA16802;
	Thu, 18 Nov 1999 02:33:37 -0800 (PST)
	(envelope-from sheldonh@FreeBSD.org)
Date: Thu, 18 Nov 1999 02:33:37 -0800 (PST)
From: <sheldonh@FreeBSD.org>
Message-Id: <199911181033.CAA16802@freefall.freebsd.org>
To: rfg@monkeys.com, sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject: Re: misc/14959: incomplete xterm termcap entry (see also bug gnu/5039)
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: incomplete xterm termcap entry (see also bug gnu/5039)

State-Changed-From-To: open->closed
State-Changed-By: sheldonh
State-Changed-When: Thu Nov 18 02:33:06 PST 1999
State-Changed-Why: 
>  Given what I now know about the behavior of `more', it now seems
>  clearer to me that ever that the Right Solution for this unfortnate
>  situation is to leave the screen save/restore capability in the
>  termcap database and then to merely add command options to programs
>  (e.g. vi, more, etc) that would say, in effect ``Don't do that!''

To quote back to you your own rantings from earlier on in the same 
thread:

>  OK.  Then you should go and make the rounds and talk with ALL of the 
>  maintainers of those programs and tell them all to add options that
>  will allow you to _disable_ the screen save/restore capabilities
>  which their authors labored to produce.

Have fun petitioning the maintainers of all the packages whose behaviour
annoys you. :-)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message