Xref: utzoo gnu.emacs.help:1465 comp.emacs:10331
Path: utzoo!utgpu!watserv1!watmath!uunet!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!tut.cis.ohio-state.edu!unreplyable!garbage
From: rms@MOLE.AI.MIT.EDU (Richard Stallman)
Newsgroups: gnu.emacs.help,comp.emacs
Subject: isearch question
Message-ID: <9103172118.AA04976@mole.ai.mit.edu>
Date: 17 Mar 91 21:18:10 GMT
References: <ROLAND.91Mar17144829@albert.ai.mit.edu>
Sender: daemon@tut.cis.ohio-state.edu
Followup-To: gnu.emacs.help
Organization: Gatewayed from the GNU Project mailing list help-gnu-emacs@prep.ai.mit.edu
Lines: 14


    I've considered using a keymap rather than the current hard-wired ickiness.
    I think I'd still have it read the keys itself rather than just using the
    command loop, so you get what you want for C-g.

C-g is an ordinary command when read by the command loop; this keymap
could redefine it.  So perhaps the ordinary command loop could be used.

For the case where C-g is typed while a command is running, perhaps
the commands could check for quits itself using inhibit-quit.

If that doesn't work, then a recursive edit won't work either.  You
would need to read characters explicitly.  But you could still mimic
a mode.