Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!agate!headcrash.Berkeley.EDU!magid
From: magid@headcrash.Berkeley.EDU (Paul Magid)
Newsgroups: comp.windows.ms
Subject: Wincomm can't do vi!
Message-ID: <1990Oct16.010437.3359@agate.berkeley.edu>
Date: 16 Oct 90 01:04:37 GMT
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Reply-To: magid@headcrash.Berkeley.EDU (Paul Magid)
Organization: ucb
Lines: 14


	When I first saw bug reports of Wincomm I was surprised to see how 
quickly they were responded to.  I have tried the program out, and I found a few
bugs of my own so I mailed the person who answered all the posted bug reports.
That was several days, ago and I have not heard a peep.  So I guess I will have
to bitch in public.   Telix has a setting called "destructive backspace"  and 
one sets this to off and vi works.  That, is if one types an "h" to move left
the left hand character is no longer erased.   I have not been able to locate an
equivalent for Wincomm, thus I must assume that this is a bug in Wincomm.
Any help will be apprecited because I want to get Wincomm to work and I am sick 
of typeing "^L".


Paul