🚀 go-pugleaf

[Et tu, line-eater?]

David B. Gaertner complains:
>... The problem I have with procomm 2.4 is that none of the terminal emulation 
> modes handle Unix's vi editor correctly.  The cursor most often appears to
> be on a line of text that is actually two or three lines above or below it, 
> or vice versa(!).  This does not happen with version 2.3.  

I had the same problem.  What is happening is you have set up procomm 2.4 to
wrap long lines.  Turn that off and the problem disappears.  (I know, you
lose some of the stuff at the end of the lines, and it is a bug, but at least
it's a work-around.)

- Tom Frauenhofer

...!seismo!rochester!ur-tut!tfra

BLOOM: You can't kill the actors!  They're human beings!
BIALYSTOCK: Oh yeah?  You ever eat with one?

In article <513@zen.BERKELEY.EDU>, c160-as@zooey.Berkeley.EDU (David B. Gaertner) writes:
> The problem I have with procomm 2.4 is that none of the terminal emulation 
> modes handle Unix's vi editor correctly.  The cursor most often appears to
> be on a line of text that is actually two or three lines above or below it, 
> or vice versa(!).  This does not happen with version 2.3.  
> 
> If it's just my copy that's messed up, I'd appreciate someone telling me so.

I can't speak for Version 2.3, but the VT52 emulator in Version 2.4 works
well enough that I can compose this reply in vi.  Perhaps you do have a 
corrupted version.

I think that VT52 is better for vi since the arrow keys work properly.
-- 
Henry M. Halff                                       Halff Resources, Inc.
halff@utah-cs.ARPA                 4918 33rd Road, N., Arlington, VA 22207

> Keywords: procomm 2.4, vt100 emulator bugs, stick with version 2.3 for now
> 
> .
> 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.
> 
> Thanks much,
> David
> ucbvax or something!zooey.Berkeley.EDU!c160-as


	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

Well, I finally got a copy of PROCOMM 2.4.1.  I can make it lose characters
on the screen at baud rates from 1200 up with a little bit of keyboard activity
while characters are coming in. 2.3 would lose characters at 19.2K baud but
2.4.1 is much worse. Response is pretty good on a monochrome screen with
a VEGA card emulating a Hercules Mono graphics or MDA but on the same vega
card acting like a CGA the response goes through the floor. There is something
REALLY wrong with this version of PROCOMM. 
We were really counting on PROCOMM here for a project in the works and
even got authorized but it looks like 2.4.1 needs serious work.
tj

I have just tried to dial the Procomm Bulletin Board number that they give
in the documentation for previous versions, and I get a disconnected number.

Does anybody know what is going on with Procomm??????

()
Mike Mitchell
myxm@lanl.arpa

In article <8725@lanl.ARPA>, myxm@lanl.ARPA (Mike Mitchell) writes:
> I have just tried to dial the Procomm Bulletin Board number that they give
> in the documentation for previous versions, and I get a disconnected number.
> 
> Does anybody know what is going on with Procomm??????
> 
> ()
> Mike Mitchell
> myxm@lanl.arpa

I believe the phone number is 314-449-9401.

-- 
Kenneth Ng: Post office: NJIT - CCCC, Newark New Jersey  07102
uucp !ihnp4!allegra!bellcore!argus!ken
     ***   WARNING:  NOT ken@bellcore.uucp ***
     !psuvax1!cmcl2!ciap!andromeda!argus!ken
bitnet(prefered) ken@orion.bitnet

McCoy: "This won't hurt a bit"
Chekov: "That's what you said last time"
McCoy: "Did it?"
Chekov: "Yes"