From owner-freebsd-questions Wed Nov 22 17:22:14 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA00898 for questions-outgoing; Wed, 22 Nov 1995 17:22:14 -0800 Received: from block.statsci.com (block.statsci.com [198.145.127.26]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA00884 for ; Wed, 22 Nov 1995 17:22:06 -0800 Received: from localhost (localhost [127.0.0.1]) by block.statsci.com (8.6.12/8.6.9) with SMTP id RAA28566 for ; Wed, 22 Nov 1995 17:21:48 -0800 Message-Id: <199511230121.RAA28566@block.statsci.com> To: questions@freebsd.org Subject: how to "fix" more(1) vs termcap/terminfo? Reply-to: scott@statsci.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <28563.817089707.1@block.statsci.com> Date: Wed, 22 Nov 1995 17:21:47 -0800 From: Scott Blachowicz Sender: owner-questions@freebsd.org Precedence: bulk Hi- This has been annoying me for a while, so...if I page something with 'more' (as found in my 2.1.0-950928-SNAP system and 2.0.5-RELEASE too, I think) with my $TERM set to "xterm", it just runs past the end of the file without waiting for a prompt or anything. Is there any way to get it to ALWAYS prompt at EOF (even for files smaller than one screen in length)? Or, if that's not possible, how do I tweak my termcap/terminfo entries to disable the screen contents save/restore? Running past the end of file without a prompt wouldn't be so bad if it didn't immediately restore the previous screen contents on exit. I usually hate it when programs do that (e.g. vi, less and FreeBSD more). Ahhh...time to go home for a LONG weekend...!!! Scott Blachowicz Ph: 206/283-8802x240 StatSci, a div of MathSoft, Inc. 1700 Westlake Ave N #500 scott@statsci.com Seattle, WA USA 98109 Scott.Blachowicz@seaslug.org