jcargill@oka.cs.wisc.edu (Jon Cargille) (04/08/91)
I'm having some flow control trouble... :( Setup: 030 Cube, 1.0a, 2400 baud modem on /dev/cua When I 'tip' out to a remote system (Unix box), I have trouble running emacs on the remote system. All my ^S/^Q characters are interpreted as flow control, and not passed through to emacs. I believe that the problem is in the software on my NeXT rather than the remote host for the following reason. If I run a remote command which produces a lot of output (such as ls -l of a large directory), and press ^S to pause the output, the screen freezes immediately, while the RD (Receive Data) indicator light on the modem continues to blaze away for a few seconds. This indicates that the local software paused, and the received data is being buffered somewhere (probably in the OS) until the buffers fill, and the remote host is told to stop transmitting. Which software would be responsible for this 'pause'? Is it tip? The problem seems to occur when I tip out from either Stuart or Terminal, so either they're blameless, or they both exhibit this problem. Is there anything that can be done about this? I know that I could bind other keys to the isearch and quote functions of emacs, but that's a gross way to hide the problem. Why can't I pass these control characters to a remote application? If you've solved this problem, please let me know. Any help is appreciated... I'd *better* get this solved, since I convinced my wife that having a NeXT would allow me to do more work from home... ;) Unrelated tip question: Why can't I set the variable 'dialtimeout' from my '.tiprc'? I get 'access denied' if the command 'dialtimeout=20' is in my .tiprc, but it works fine if I type it by hand after ~s. Is this a bug? Is it fixed in 2.0? Please email; I'll summarize unless this is all attributable to my own stupidity... ;) Thanks, Jon Cargille jcargill@cs.wisc.edu