🚀 go-pugleaf

In article <9105150902.AA18293@telotech.UUCP> bsa@telotech.ai.mit.edu writes:
> +---------------
> | In article <1991Apr29.204040.14429@jato.jpl.nasa.gov> dave@jato.jpl.nasa.gov (Dave Hayes) writes:
> |    I have one HOWEVER I am reluctant to release it for general use until I
> |    find out exactly how to stop an ESC from being eaten by a search command.
> | 
> | Here's the fix I use.  Apply the diff to the source or to your own private
> | copy of isearch.el.
> | 
> | +		    ;; jbw: added support for unreading ESC if it might be
> | +		    ;; part of a character sequence generated by a
> | +		    ;; function key.  This is timing dependent and will
> | +		    ;; not always work.
> +---------------
> 
> There's a MUCH cleaner way:
> 
> (setq search-exit-char ?\r)
> 
> ++Brandon

This is definitely cleaner, but does not solve the problem jbw put
the fix in for, namely typing of arrow keys (containing and ESC)
while in an isearch.  By putting in your fix, when he types
an arrow key while in isearch, it will merely beep at him, it will
not terminate the search AND PERFORM MOVEMENT ALSO, which is
what he wants and what his fix solves.  Thanks for a novel
solution which may help other people who do not like to end
an isearch with ESC.
--
-----
	Dion Hollenbeck             (619) 455-5590 x2814
	Megatek Corporation, 9645 Scranton Road, San Diego, CA  92121
        uunet!megatek!hollen       or  hollen@megatek.uucp