🚀 go-pugleaf

In article <3694@tymix.UUCP> pnelson@hobbes.UUCP (Phil Nelson) writes:
>In article <25530@usc.edu> papa@pollux.usc.edu (Marco Papa) writes:
>>In article <3675@tymix.UUCP> pnelson@hobbes.UUCP (Phil Nelson) writes:
>>|I had this problem cutting from and pasting to A-Talk III Release 1.0e,
>>|it will paste back 256 char max.
>>
>>I just received the latest snap from Mikael, and checked with A-Talk III
>>1.3a (the current version).  It works like a champ.  I "snapped" an entire 
>>page from a file I was "more"-ing on the Amiga, and sent it to
>>my host connected with A-Talk III and running Gnu-Emacs.  It snapped all
>>600+ characters with no problem. I tried with AT-/// Release 1.0e, with same
>>results. Maybe you don't know how to use it :-)
>
>Maybe. Then again, maybe your program does not like having chars rammed
>down it's input buffer :-)

Nah.  My program never had any problem of that kind.  I actually rammed
4K down its input buffer and it took it no problem.

>I was able to snap text larger than 256 chars by using the "snap -c20"
>suggested elsewhere (thanks, whoever made the suggestion). I have since
>upgraded to A-Talk3 version 1.3a, just now I went back to "snap" without
>any args, and the same problem of not being able to paste back more than
>256 characters has recurred, every time I try it. I can paste back the
>same snap into CED, slow, but it works.

My suggestion is wait for the new snap.  As I said the problem is NOT with
A-Talk III.

>Some things that may be somewhat unusual with my setup: I use morerows (but
>the separate screen setting of A-Talk) and XOn-XOff.

Does the problem appears when you DON'T use morerows and you DON'T use
X-on/X-off?  Those two experiments would have been the first ones
I would have tried.  BTW, Xon/X-off with AT-/// is useless at baud rates
less thasn 9600.

>I am curious as to what your program does with keyboard input after it has
>received an X-Off from the DCE - does it toss the input? don't panic - it's
>just curiosity, 

It will just respect the X-off. The keyboard input gets backed up on the
input queue, until the X-on arrives, at which point it is sent back out
the serial port.

>I don't think the Consat is sending an X-Off at 256 chars
>(I'm not sure, since it is a little difficult to know the configuration
>of a Consat without special license, which I don't have in my present job)
>but it might be. 

That should be fairly easy to check.  Turn off X-on/X-off handshake.
Select Capture Plain (so that control chars are retained).  Open a
capture buffer. Snap the buffer > 256 chars. After you're done, close
the capture buffer, and check whether the X-off is there.

-- Marco
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
"Xerox sues somebody for copying?" -- David Letterman
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=