home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.sysv386
- Path: sparky!uunet!spool.mu.edu!uwm.edu!linac!att!cbnews!adh
- From: adh@cbnews.cb.att.com (andrew.d.hay)
- Subject: Re: vi error "Tmp file too large"
- Organization: AT&T
- Date: Tue, 15 Dec 1992 16:14:11 GMT
- Message-ID: <1992Dec15.161411.22802@cbnews.cb.att.com>
- References: <215@ucla-an.UUCP>
- Lines: 34
-
- In article <215@ucla-an.UUCP> daveh@ucla-an.UUCP (Dave Hammond) writes:
- "
- "On a WYSE system running their flavor of UNIX 3.2, I get an error
- "from vi, "Tmp file too large" when I attempt to edit a file of
- "more than ~5000 lines. I've done this on several other systems
- "(SCO XENIX, SCO UNIX, ALTOS UNIX, BSD) without any problems.
- "
- "Is this a well known UNIX 3.2 problem?
-
- i'd say yes.
-
- "Is there a patch or workaround for this problem?
-
- several people have been close...
-
- it's a vi problem, but not with pdp11 being #defined; rather, with
- vmunix _not_ being #defined, which makes vi _think_ it's on a pdp-11.
- this results in a fixed 256K tempfile, as others have noted. with
- vmunix #defined, vi dynamically allocates space for the tempfile.
-
- oddly, there are _separate_ #defines for bsd, usg, and vmunix. i
- found this out when i hit the tmpfile limit once too often and got
- thoroughly irritated. i grabbed the src [sVr3.1.1], uncommented the
- vmunix #define, recompiled, and presto! had a vi that worked fine on
- 1M+ files.
-
- complain to your vendor -- there's no excuse except laziness/ignorance
- for them not to fix vi.
-
- --
- +--------------------------------------------------------------+
- Andrew Hay | one step beyond the outer limits of the twilight |
- a_d_hay@att.com | zone in the darkened room at the night gallery |
- +--------------------------------------------------------------+
-