Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!rutgers!iuvax!silver!creps
From: creps@silver.bacs.indiana.edu
Newsgroups: comp.emacs
Subject: Gnu Emacs ^Q & ^S problems
Message-ID: <20600002@silver>
Date: Tue, 3-Nov-87 20:33:00 EST
Article-I.D.: silver.20600002
Posted: Tue Nov  3 20:33:00 1987
Date-Received: Sat, 7-Nov-87 09:01:17 EST
Organization: Indiana University BACS, Bloomington
Lines: 26
Nf-ID: #N:silver:20600002:000:1324
Nf-From: silver.bacs.indiana.edu!creps    Nov  3 20:33:00 1987


   I'm having a little trouble with using Gnu Emacs, in that the thing
thinks that flow control characters (^Q ^S) are commands. So, every time
there is a lot of stuff going to the screen, the flow control characters
get sent, and are interpreted as search commands. Then more stuff gets
sent asking what to search for, more ^Q's and ^S's, then the terminal
starts beeping, and so on, until I have to type about 100 ^Z's to stop
the thing.

   Not having a Gnu Emacs manual that I can find, I'm asking for help here.
The closest thing I've come up with to fix this is binding ^Q and ^S to
what-cursor-position. Then whenever flow control is inserted, it just
prints information on the status line. But even this doesn't completely
fix it, since sometimes when this happens the screen is messed up.

   What I'm looking for is some kind of a null command, that will do nothing,
not even print to the status line. Just unsetting ^Q and ^S won't work,
because undefined keys cause a ^G (bell) to be sent, and the old problem
of the "infinite" loop of ^G's starts again.

   I would appreciate any help on this.
-	-	-	-	-	-	-	-	-
Steve Creps on the VAX 8650 running Ultrix 2.0-1 at Indiana University.
	creps@silver.bacs.indiana.edu
"Well, I noticed the lad with the thermonuclear device was the Chief
 Constable for the area."