chris@grkermit.UUCP (Chris Hibbert) (06/26/84)
(I originally posted only my query to net.emacs, but I'm expanding to include net.unix-wizards since I've gotten information that the tty driver has or had a bug that is causing part of the problem.) My basic problem is that vt100's, Unipress Emacs, and a new 4.2BSD system are fighting amongst themselves about flow-control characters. I've solved the problem within Emacs by increasing the padding so that the terminal never generates a ^S there. The problem now is that if you use ^s (e.g. to do a search) within emacs, then when you leave emacs, the terminal freezes in the middle of the first command with reasonably long output. I have been told (by genrad!john) that this is due to a bug in the tty driver that causes it to record flow-control characters even in raw mode. He said that fixes were announced for 4.1, and he was surprised that they weren't incorporated into 4.2. Does anyone have a copy of the fix they could send me? Am I on the right track? Thanks again, Chris decvax!genrad!grkermit!chris allegra!linus!genrad!grkermit!chris
chris@grkermit.UUCP (Chris Hibbert) (07/09/84)
(I originally posted a similar query only to net.emacs. I'm expanding my question to include a kernel question, so I've expanded the group list as well.) My basic problem is that vt100's, Unipress Emacs, and a new 4.2BSD system are fighting amongst themselves about flow-control characters. I've solved the problem within Emacs by increasing the padding so that the terminal never generates a ^S there. The problem now is that if you use ^s (e.g. to do a search) within emacs, then when you leave emacs, the terminal freezes in the middle of the first command with reasonably long output. I have been told (by genrad!john) that this is due to a bug in the tty driver that causes it to record flow-control characters even in raw mode. He said that fixes were announced for 4.1, and he was surprised that they weren't incorporated into 4.2. Does anyone have a copy of the fix they could send me? Am I on the right track? By The Way, is our problem related to the fact that all terminals (except dial-ups) run at 9600 baud? Thanks again, Chris decvax!genrad!grkermit!chris allegra!linus!genrad!grkermit!chris
chris@umcp-cs.UUCP (07/10/84)
Hm - what you describe (the screen freezing) isn't what happens to
us. Instead, our VT100s just drop characters if you exit Emacs
after doing a ^S (without a ^Q). This is because the VT100 is so
smart that it ``knows'' the computer has already been told to shut
up, so it doesn't send any more ^Ss. (A good idea, but it just
doesn't work well in this case.) The fix for this problem is to
simply hit control-Q after exiting Emacs, if you're on a VT100.
--
In-Real-Life: Chris Torek, Univ of MD Comp Sci (301) 454-7690
UUCP: {seismo,allegra,brl-bmd}!umcp-cs!chris
CSNet: chris@umcp-cs ARPA: chris@marylandgail@calmasd.UUCP (07/11/84)
We recently installed UniPress's EMACS, and have been having
similar problems. I'm hereby adding another plea for a fix for
this, if one is available. Please, no kernel changes -- we
don't have a source license yet.
Gail Hanrahan
{decvax,ucbvax}!sdcsvax!calmasd!gail
Calma Company, San Diegoscs@foxvax1.UUCP (S.C. Schwarm ) (07/23/84)
I was able to get around the XON/XOFF problem on #85 of EMACS by using Cbreak mode on the terminal. My problem at the time was we are using a Sytek network for our terminals as a result the flow control request had nothing to do with the characters being sent(padding never works). I have a diff file, but I have not updated it for 264 because we now use Able MUXes with hardware flow control. I'll send the diff file to anyone who wants it. Steve Schwarm decvax!genrad!wjh12!foxvax1!scs
softech@othervax.UUCP (08/07/84)
[Fix this please] ^S and ^Q are so imbedded into the tty drivers that we simply decided to use other keys (^F for forward search, ^V for quote-character) and to bind the XON and XOFF keys to novalue (or nothing). Occasionnally we have to do a redraw-screen (especially when returning to a stopped emacs) because the emacs driver is a little too fast for the VT100 (and VT131). This is a very simple fix, all you have to do is add four lines to your .emacs_pro file: (bind-to-key "novalue" "^S") (bind-to-key "novalue" "^Q") (bind-to-key "search-forward" "^F") (bind-to-key "quote-character" "^V") Richard Blouin, SofTech Inc. !philabs!othervax!softech