🚀 go-pugleaf

Hi... File capture doesn't seem to work in the new version of UniTerm.
When I start file capture using alt-C, the dialog goes through fine, but
nothing that I type or the remote machine sends back gets echoed on the
screen (i.e., the screen just goes dead until I stop file capture).  I
can see something is getting transferred because the cursor flickers.
After stopping the capture, it comes back to normal.  However, the capture
file doesn't have ASCII data in it (when I type it on the screen, I get an
-- END OF FILE -- message right away) even though the file length looks
ok in the directory listing.

Has anyone else encountered this bug or knows how to fix it?  For the
time being I've gone back to using the old UniTerm since I use the file
capture feature.  I would appreciate it if someone (Simon?) could send
me a fix.

Another question:  What came of the terminal lockup debate?  I ran into
this problem yesterday while using UniTerm.  Has this been tracked down?

-- Ashwin.

ARPA:    Ram-Ashwin@yale
UUCP:    {decvax,linus,seismo}!yale!Ram-Ashwin
BITNET:  Ram@yalecs

P.S.  A suggestion:  If you called DEFAULT.SET something like UNITERM.SET
or UNITERM.OPT instead (like Kermit does), all the UniTerm files will list
together in the directory listing, making it easier to copy them all to
RAMDISK in one stroke (rather than having to hunt for DEFAULT.SET at the
other end of the directory listing).

-------
-------