From owner-freebsd-current Sun Oct 20 14:26:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA15550 for current-outgoing; Sun, 20 Oct 1996 14:26:25 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA15545 for ; Sun, 20 Oct 1996 14:26:23 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA13401; Sun, 20 Oct 1996 15:26:13 -0600 (MDT) Date: Sun, 20 Oct 1996 15:26:13 -0600 (MDT) Message-Id: <199610202126.PAA13401@rocky.mt.sri.com> From: Nate Williams To: Paul Traina Cc: cracauer@wavehh.hanse.de, freebsd-current@freebsd.org Subject: Re: xterm termcap definition In-Reply-To: <199610201726.KAA17317@precipice.shockwave.com> References: <9610201037.AA23601@wavehh.hanse.de> <199610201726.KAA17317@precipice.shockwave.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Regarding the alternate screen behaviour: > > I think the "alternate screen" feature should *not* be enabled bu > default, too many people are used to one-screen behaviour (i.e. the > last screen of output of more/less is still displayed when more > exits). Eric's and NetBSD's entries have alternate screen enabled and > should be changes before importing them to FreeBSD. I aplogize for > overlooking this. > > I disagree. The alternate screen behavior is the canonical behavior for > XTerms. It's been freebsd that's been different all this time, and I recall > just how much this torqed me off when I switched to freebsd. I *totally* disagree. The alternate screen behavior has never been standard in *any* xterm system I've used. To note: HP/UX, Ultrix, SunOS, Solaris, VMS (yeah, VMS), 386BSD, FreeBSD, NetBSD, OSF/1, and Digital Unix. Should I go on? None of them xterm entries used the alternate screen behavior by default. Nate