Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!imci5!imci4!newsfeed.internetmci.com!feed1.news.erols.com!howland.erols.net!nntp.crl.com!Symiserver2.symantec.com!news From: tedm@agora.rdrop.com Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: bad vt102/vt220 termcap entry in FreeBSD 2.1? Date: 6 Oct 1996 16:30:52 GMT Organization: Symantec Corp. Lines: 16 Message-ID: <538mrs$b9d@Symiserver2.symantec.com> References: <rreiner.844306769@nexus.yorku.ca> Reply-To: tedm@agora.rdrop.com NNTP-Posting-Host: shiva1.central.com X-Newsreader: IBM NewsReader/2 v1.2.5 In <rreiner.844306769@nexus.yorku.ca>, rreiner@nexus.yorku.ca (Richard Reiner) writes: >Several different terminal emulators, none of which have shown errors >before, seem to have trouble with the vt102 termcap entry shipped w/ There is an excellent vt100 testing utility floating around called vttest or some such that has a whole procedure for spitting out serieses of VT100 codes to test various terminal emulators. I've used it to test a lot of Windoze emulators and it is incredible how badly they behave. I've had the best luck with honest-to-god vt100 compatible actual terminals. You can also use this terminal program to figure out what series of command codes your terminal emulator is misinterpreting and then go into the termcap entry and strike out that feature.