Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!olsen
From: olsen@XN.LL.MIT.EDU (Jim Olsen)
Newsgroups: comp.emacs
Subject: Re: spurious i-search
Message-ID: <755@xn.LL.MIT.EDU>
Date: Fri, 16-Oct-87 14:29:19 EDT
Article-I.D.: xn.755
Posted: Fri Oct 16 14:29:19 1987
Date-Received: Sat, 17-Oct-87 22:46:13 EDT
References: <8710151837.AA10134@mitre-bedford.ARPA>
Organization: MIT Lincoln Laboratory, Lexington, MA
Lines: 25

In a recent article, jfjr@MITRE-BEDFORD.ARPA (Freedman) writes:
>I am using a vt100 on Ultrix running Emacs 18.49.  I find I get
>"Failing-isearch: ^Q" often enough to tempt me into encouraging my
>terminal to go airborne.  [The solution] which seems to work is to
>evaluate (set-input-mode nil t).

>Now here's my question(s). The author of problems describes this solution
>as drastic and enough to get emacs "semi" working. Well gee, it seems to
>work fine.  Am I missing something?  What dangers am I skirting?

There are no hidden dangers in using (set-input-mode nil t).  However,
it does mean that ^S and ^Q are no longer available, so you may want
to rebind their functions to other keys.  I have bound isearch-forward,
quoted-insert, and save-buffer to keypad keys on my VT100.  I have
also redefined some of the search control characters, using:

		(setq search-repeat-char ?\C-z)
		(setq search-exit-char ?\C-x)
		(setq search-quote-char ?\C-c)

to make searching more convenient.  Emacs works fully and completely for me.

Apparently, the author of 'problems' thinks systems using XON/XOFF
flow-control are "brain-damaged" and should go away.  Fortunately, one
needn't accept all of the GNU philosophy in order to use GNU software.