Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxj!mhuxn!houxm!ihnp4!zehntel!hplabs!hao!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.bugs.4bsd
Subject: Re: nonoptimal vi behavior
Message-ID: <1544@umcp-cs.UUCP>
Date: Mon, 3-Dec-84 18:12:08 EST
Article-I.D.: umcp-cs.1544
Posted: Mon Dec  3 18:12:08 1984
Date-Received: Thu, 6-Dec-84 05:35:24 EST
References: <2836@ucbcad.UUCP>
Distribution: net
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 13

I haven't looked at the source to VI for ages and ages (how does one
express this in terms of sagans? :-) ), but it seems like making vi use
al & dl rather than cs should be a relatively simple fix, considering
that the change to make it use cs was added between 4.1 and 4.2....  I
think the screen updates for insert & delete line are done someplace
deep inside ``ex_vadj.c'', or you could always just have the startup
code forget about the ``cs'' string if both al and dl exist!
-- 
(This line accidently left nonblank.)

In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (301) 454-7690
UUCP:	{seismo,allegra,brl-bmd}!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@maryland