🚀 go-pugleaf

[]
This was a reply to my earlier posting:

>From: latham@bsdpkh.UUCP (Ken Latham)
>
>> .
>> The problem I have with procomm 2.4 is that none of the terminal emulation 
>> modes handle Unix's vi editor correctly.
>> 
>> If it's just my copy that's messed up, I'd appreciate someone telling me so.
>> 
>
>	OK ... I`'ll tell you    "It is only your copy that is messed up."
>
>	Mine works fine!!!!!!!  ( vt-100 haven't used the others )
>
>
>		Ken Latham, AT&T-IS (via AGS Inc.), Orlando , FL
>		uucp: ihnp4!bsdpkh!latham

In reply to this response as well as to a letter I received from San Diego,
I will describe my experience with Procomm's vt-100:

I used nothing but version 2.3 until I heard that version 2.4.1 was released.
So, apparently it was not just my copy that was messed up.
I tried it out, and yes, they fixed the bug that I was talking about.  I know
that people suggested turning off word wrap, but for some of the things I do, I can't use it. 
But even though the bug is fixed, I don't think it's fixed
enough.  When the cursor appears to be on a different line than it really
is, it could simply rewrite the letters underneath so that one knows for sure
where the cursor is.  IN VI, TRY TO TYPE A LINE LONGER THAN 80 CHARS TO 
SEE FOR YOURSELF WHAT I MEAN (with LINE-WRAP and SCROLL _ON_).  Be sure to
move the cursor using both the arrow keys and w and b.

But even though Procomm has this minor problem, I still think it's the best
comm program out there.  I heartily recommend it to everyone.

David Gaertner
ucbvax!zooey.Berkeley.EDU!c160-as