From owner-freebsd-questions Sat May 9 15:01:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05749 for freebsd-questions-outgoing; Sat, 9 May 1998 15:01:01 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from castor.loco.net (lucy.bedford.net [206.99.145.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05681 for ; Sat, 9 May 1998 15:00:47 -0700 (PDT) (envelope-from listread@bedford.net) Received: (from listread@localhost) by castor.loco.net (8.8.8/8.8.8) id RAA10348 for freebsd-questions@freebsd.org; Sat, 9 May 1998 17:58:33 -0400 (EDT) (envelope-from listread) Message-Id: <199805092158.RAA10348@castor.loco.net> Subject: Xterm, termcap, and LINES To: freebsd-questions@FreeBSD.ORG Date: Sat, 9 May 1998 17:58:33 -0400 (EDT) Reply-to: djv@bedford.net From: CyberPeasant X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Recently having installed 2.2.6, I have noticed a problem with terminal settings. Xterm is being run from a second machine (OpenBSD 2.1 on Pmax hardware), invoked from a window manager running on X11R5 there, although the xterm is X11R6. (This is the normal configuration for this machine/OS). xterm is started with a line like so: xterm -T "Castor" -n "Castor" -wf -e rlogin -8 -l username castor I.e., xterm is executing on the pmax. When the rlogin completes on host castor (the Freebsd host), /sometimes/ the LINES variable is set to 24, which agrees with the size of the window. At other times, it is set to a larger value, namely 65. This is unpredictable, sometimes occuring in several successive openings, sometimes not being seen for days. The 65 value is the one listed in /etc/termcap under xterm, "li:65". In all cases, the TERM variable is correctly set to xterm. The same invocations of xterm have always returned a consistently correct LINES setting when the rlogin host was Linux or NetBSD. An obvious workaround is to alter /etc/termcap to the "old" li:24 entry, and I would like to do that. But F'bsd uses an unfamiliar (libmytinfo) terminal info system, that combines terminfo and termcap in a single /usr/share/misc/termcap.db, the interface to which I incompletely understand to be tconv. But is there a fix? What is the righteous procedure to change the definition of xterm, so that it is reflected "everywhere"? (i.e. so that all apps get the li:24, regardless of whether the app queries via a termcap routine or a terminfo routine). Ah, yes, the shell in use on the FreeBSD is bash 2.02. (The problem was evident with 2.01, as well). Could this be a bash problem? TERM=${TERM:-cons25} appears in user's .profile I have commented out these lines: # make mail(1) happy: # export crt=24 since I do not care about mail's mood, and have no idea what crt is about, and do not export variables I have never seen before. Dave -- <----. mail-to: djv@bedford.net <----|=================================== <----' Zber Qnrzbaf, Srjre Qrivyf! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message