🚀 go-pugleaf

In article <2150@sdcsvax.UCSD.EDU> rick@beowulf.UUCP (Rick Randall) writes:
>In article <216@dayton.UUCP> sjm@dayton.UUCP (Steven J. McDowall) writes:
>>
>>Having used Procomm 2.4.1 (tm) for a little while now, I still have
>>found these various bugs (same as 2.4 suprise!):
>>
>>    1)  When in vt-100 mode, and in line-wrap (auto wrap) it still
>>        wraps at the 80'th character, even if the next character is

...when downloading with KERMIT ...
>>        convert N/L (ie. Line Feeds) into C/R L/F pairs. Even if you specify
>>        a binary file transfer. Needless to say, this wrecks havok. 

I am writing this with version 2.4.2, just released, and have to say that the 
line wrap problem has been alleviated, tho not completely cured. Using vi, the
text will either jump down two lines or reverse feed one line if one tries to
write off the end of the line. A ^L clears it all up... minor, but annoying.

More serious is the inability of PROCOMM to use kermit to transfer binaries in
a consistant fashion. The LF to CR/LF problem can be fixed from the setup menu
in the terminal section. In spite of this, binaries are a hit or miss 
proposition at best. Text kermit xfer's up and down work admirably...(sigh).


-- 
             ====================================================  
             |    Fortiter in re,       ||     Bill Fischer     |
             |       suaviter in modo.  ||  ...ihnp4!chinet!wmf |
             ====================================================