From owner-freebsd-bugs Sat Jun 27 04:40:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA03930 for freebsd-bugs-outgoing; Sat, 27 Jun 1998 04:40:25 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from totem.tihlde.hist.no (anders@totem.tihlde.hist.no [158.38.48.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA03901; Sat, 27 Jun 1998 04:40:16 -0700 (PDT) (envelope-from anders@totem.tihlde.hist.no) Received: (from anders@localhost) by totem.tihlde.hist.no (8.8.8/8.8.8) id NAA00164; Sat, 27 Jun 1998 13:40:09 +0200 (CEST) (envelope-from anders) Message-ID: <19980627134009.A132@totem.tihlde.hist.no> Date: Sat, 27 Jun 1998 13:40:09 +0200 From: Anders Nordby To: freebsd-questions@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: FreeBSD and Terminal capabilities Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i X-Operating-System: FreeBSD 2.2.6-RELEASE X-Disclaimer: Listen, and thou shall not fear. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ever since I started off with FreeBSD, I've had trouble with termcap. It started with NCFTP v2.4.2 (giving funny characters like $<$<2>2>> on the screen with vt100 emulation). I was adviced to use vt220 emulation instead, and so I did (not fixing anything). Later on I found problems with 'screen' (the screen manager), giving me a jumpy display (when text scrolls up one line, it is diaplayed one line above that for a short flash -- thus giving a jumpy effect) with certain applications. I tried screen with vt100 and vt102 in addition to the original screen one, not making a difference. Would I be on the wrong track blaming the FreeBSD termcap? It does seem quite old and unupdated. Is there any way to change or update it, or is there something else I can do? Termlib? I tried installing a newer BSD'ish termcap, unsuccessfully (it didn't work at all). PS: I'm using CRT (which is considered to be the best (?) terminal emulator for Windows) to log in. I've also tried several others, experiencing the same problems. PS2: My host is running FreeBSD 2.2.6-STABLE, upgraded from 2.2.5. I've tried running the same applications with Solaris and Linux hosts, free of any mentioned problems. PS3: From the: ncftp autoconfig: checking for -ltermcap... yes checking for -lcursesX... no checking for -lcurses... no configure: warning: Did not detect curses, but trying again with termcap: checking for -lcurses... (cached) no checking for -lcurses... yes checking for -ltermlib... no checking for -lncurses... yes screen autoconfig: checking for libcurses checking for libtermcap - you use the termcap database -- Anders Nordby ^ anders@fix.no ^ http://anders.fix.no/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message