Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!rpi!masscomp!peora!tarpit!bilver!bill From: bill@bilver.uucp (Bill Vermillion) Newsgroups: comp.unix.admin Subject: Re: vi "TMP file too large" error Keywords: vi memory Message-ID: <1991Feb26.152650.12458@bilver.uucp> Date: 26 Feb 91 15:26:50 GMT References: <1991Feb21.183218.8617@convex.com> <1991Feb22.142239.16509@tygra.UUCP> Organization: W. J. Vermillion - Winter Park, FL Lines: 24 In article <1991Feb22.142239.16509@tygra.UUCP> cat@tygra.UUCP (CAT-TALK Maint. Account) writes: >In article <1991Feb21.183218.8617@convex.com> tchrist@convex.COM (Tom Christiansen) writes: >"Thank AT&T. Their vi, or at least some of its incarnations, has a >"filesize limit. Get the real vi from BSD or Sun and the problem will go >"away. If you can't do that, flame your vendor. >Ditto SCO XENIX's vi (its probably a SYSV clone). It'll handle just under >500k before spitting out that message. We have ELVIS and STEVIE, but they >can't handle using TERMINFO instead of the error-riddled TERMCAP and the >arrow keys don't work at 2400bps or lower. Well there must be different versions of SCO's vi, because I have one that I have had files larger than 2 megs that I have edited. The Unix V.2.3 from Esix on another system I have dies at about 400k max. As a matter of fact I copied the vi from SCO onto the Unix box (I own them both). Just grabbed the history file and loaded in 50272 lines at 3,177,657 byte in size. This is SCO Xenix 2.3.0 with development system. -- Bill Vermillion - UUCP: uunet!tarpit!bilver!bill : bill@bilver.UUCP