Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!ucbcad!ucbvax!LF-SERVER-2.BBN.COM!jr
From: jr@LF-SERVER-2.BBN.COM.UUCP
Newsgroups: comp.emacs
Subject: Re: Gnu Emacs ^Q & ^S problems
Message-ID: <8711191559.AA23287@ucbvax.Berkeley.EDU>
Date: Thu, 19-Nov-87 10:59:26 EST
Article-I.D.: ucbvax.8711191559.AA23287
Posted: Thu Nov 19 10:59:26 1987
Date-Received: Sat, 21-Nov-87 15:43:46 EST
References: <864@investor.UUCP>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: jr@ALEXANDER.BBN.COM
Organization: The ARPA Internet
Lines: 26

> I had the same problem with uEmacs so I modified the input routines to
> pass ^S and ^Q.  I imagine you could do the same thing in gnu.  Of course
> this will not make emacs experts very happy since you will have to rebind
> the routines called by these keys to something else.  I uses M-/ for ^S,
> since it was similar to vi.

GNU emacs gives you some other options (this comes up so often we
should just repost it every now and then, like the usenet etiquette
messages.)

1.  You can run in CBREAK mode with the kernel handling flow control.
Issue (set-input-mode nil t) from your .emacs.  This leads to the
problem above that you have to bind other keys to isearch-forward and
quoted-insert.  Traditional nominees are C-^ and C-\.  There is a
further problem, however; the interactive key set inside isearch
includes ^S and there is no convenient way to change this (yet).

2.  You can use the keyboard-translate-table to cause, say, C-^ and
C-\ to be received by emacs as though you had typed ^S and ^Q.  This
avoids the problem above, since even the insides of iearch will be
fooled.

I think I'll save this file away for future use.

/jr
jr@bbn.com or jr@bbn.uucp