Path: utzoo!attcan!uunet!aplcen!unmvax!uokmax!uokmax.ecn.uoknor.edu!butch
From: butch@uokmax.ecn.uoknor.edu (H. G. Walker)
Newsgroups: comp.windows.ms
Subject: Re: Wincomm can't do vi!
Message-ID: <1990Oct16.133718.11636@uokmax.ecn.uoknor.edu>
Date: 16 Oct 90 13:37:18 GMT
References: <1990Oct16.010437.3359@agate.berkeley.edu>
Sender: news@uokmax.ecn.uoknor.edu (Nets)
Reply-To: butch@geo785.gcn.uoknor.edu
Organization: University of Oklahoma, Norman,OK 73019
Lines: 21

In article <1990Oct16.010437.3359@agate.berkeley.edu>, magid@headcrash.Berkeley.EDU (Paul Magid) writes:
|> 
|> 	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".

Sorry for the delay.  I have been flooded with suggestions and bug reports and
several of them concerned this problem.  I responded to several but I may have
overlooked yours.  The problem is that Wincomm currently assumes a destructive
backspace.  Synappsys is exploring the possible fixes for this problem as to 
which would be most convenient.  They will fix the problem, but there are
several other little bugs to be fixed also, so it may take a few days.  Sorry.

Butch