From owner-freebsd-hackers Thu Nov 5 18:00:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03471 for freebsd-hackers-outgoing; Thu, 5 Nov 1998 18:00:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03466 for ; Thu, 5 Nov 1998 18:00:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA01574; Thu, 5 Nov 1998 17:58:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811060158.RAA01574@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: ncurses update? In-reply-to: Your message of "Fri, 06 Nov 1998 09:57:13 +0800." <199811060157.JAA08921@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Nov 1998 17:58:44 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > Coming out of a discussion on the -alpha list, I was contacted about > > this. We're still at 1.8.6. What's the justification for not > > upgrading? > > I've got a bmaked version running on one of my systems and it has been in > that state for quite some time. > > I find very few problems with it as a result.. One thing I was very much > tempted to do was to grab the OpenBSD termcap reader that generates the > terminfo style tables that ncurses can use directly. The beauty of that > is that the result is both libtermcap and libncurses compatable. The > other nice thing it does (I think) is support a terminfo.db file rather > than thousands of tiny binary files. So, you can have a text file (just > like termcap) and do a cap_mkdb on it for fast lookups. > > The ncurses version of the termcap reader is pretty rotten (IMHO). It > had some 'getcap' compatability code added for 4.4BSD compatability, but > then they built in a castrated version of getcap that didn't support .db > files etc. Ok. Can we assume this is in your queue, or should we find an eager go-getter to look after it? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message