Xref: utzoo comp.sys.att:12051 comp.editors:2802
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!linac!att!cbnewsh!wcs
From: wcs@cbnewsh.att.com (Bill Stewart 908-949-0705 erebus.att.com!wcs)
Newsgroups: comp.sys.att,comp.editors
Subject: Re: AT&T Unix Sys V (from AT&T); how do I get bug fixes?
Message-ID: <1991Mar26.033719.14987@cbnewsh.att.com>
Date: 26 Mar 91 03:37:19 GMT
References: <221@picker.Picker.COM> <1991Mar21.215229.3618@banzai.PCC.COM>
Organization: Your typical phone company involved in your typical daydream.
Lines: 31

In article <1991Mar21.215229.3618@banzai.PCC.COM> john@banzai.PCC.COM (John Canning) writes:
]In article <221@picker.Picker.COM> gaeta@pacs.picker.com (jay gaeta) writes:
]>I am running AT&T Unix Sys V Rel. 3.2.2 (from AT&T).  There are a
]>couple of bugs that I would like to get a fix for:
]>
]>1) The vi editor won't work on large files.  (I know I can get
]>public domain versions and port them but it seems like a brute force
]>approach.)

	Sigh.  I wish they'd fix this, it's trivial.
	About N>8 years ago, I fixed this for vi Version 3.7,
	the termcap version, on the machines I was running.
	Editing N-Megabyte files was very convenient.

	Do you have source?  It's probably changed somewhat, but 
	the right combination of compile-time options did the trick.
	The basic issue was that the VMUNIX flag told vi two things:
	- you've got virtual memory, so make your tables nice and big,
	- you're running Berkeley Unix, so do something-or-other
		and there was a flag to turn it back off.
	

]Call the AT&T Hotline at 800-922-0354.  When you purchased Unix, you
]also purchased 90 days of free support for the product.  

	It's worth a try.  Or get GNU emacs, and use vi-mode.
-- 
				Pray for peace;
					Bill
# Bill Stewart 908-949-0705 erebus.att.com!wcs AT&T Bell Labs 4M-312 Holmdel NJ
# Hacker.  System Designer.  Troublemaker.