Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!pravda.aa.msen.com!spool.mu.edu!howland.reston.ans.net!swrinde!elroy.jpl.nasa.gov!decwrl!purdue!news.bu.edu!acs2.bu.edu!mi From: mi@bu.edu (Mikhail Teterin) Newsgroups: comp.unix.bsd.freebsd.misc Subject: xterm's termcap entry Date: 25 Oct 1995 14:33:31 GMT Organization: Boston University Lines: 32 Message-ID: <46lhrr$p4p@news.bu.edu> NNTP-Posting-Host: acs2.bu.edu Summary: "termcap entry too long" Keywords: TERMCAP,SunOS,xterm,cons25 X-Newsreader: TIN [version 1.2 PL2] To work on the UMass' computers (various Suns running old SunOS) I trans- ferred my /etc/termcap over there to my account and set the TERMCAP envi- ronment variable to ~/termcap. Now cons25, cons30, etc., are recognized and all the screen oriented prog- rams run perfectly (elm, vi, tin, etc.) However, SunOS was not smart eno- ugh at the moment it was installed over there -- when TERMCAP is set, it will not look into system wide termcap file (in /etc) for the terminal- types not listed localy. So, I have to keep everything in my local termcap. Ok. The entry for the xterm crashes the tcsh (and everything else, which was linked with old termcap-libraries). It can only say: "termcap entry too long" and gives me a bus-error -- obviously, they do not allocate buffer long enough (man says it is 1024). The xterm's entry is indeed long, it includes vt220, which includes vt100 and so on. I don't mind using Sun's own idea of xterm, but I do not want to abandon the features people put into FreeBSD's xterm's entry (there should be something, if it is so long!) (-: If I don't use X, TERM correctly sets to cons25 (or 30). Everything is fine, but '~' sign is shown as '\^' by vi. If anyone feels like commenting this, I'll sure appreciate it! Thank you for reading! -mi (All the programms I use on the Suns seem to ignore TERMINFO) -- hot-dog apple-pie baseball Chevrolet