Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!rutgers!cmcl2!yale!Ram-Ashwin
From: Ram-Ashwin@cs.yale.edu (Ashwin Ram)
Newsgroups: comp.emacs
Subject: Re: ARGH!  Ahem.  Umm, answering prompts & abbreviating
Message-ID: <49905@yale-celray.yale.UUCP>
Date: 7 Feb 89 17:00:20 GMT
References: <35648@bbn.COM> <8902061849.AA06423@NMSU.Edu>
Sender: root@yale.UUCP
Reply-To: Ram-Ashwin@cs.yale.edu (Ashwin Ram)
Organization: Computer Science, Yale University, New Haven, CT 06520-2158
Lines: 14
In-reply-to: jthomas@nmsu.EDU

In article <8902061849.AA06423@NMSU.Edu>, jthomas@nmsu.EDU writes:
> On the other hand, yes-or-no-p has another difference from y-or-n-p.
> y-or-n-p reads one and only one character.  If it's a "y" or "Y", t, else
> nil.  That includes characters like C-x .
> 
> I am very happy to be allowed to switch buffers, fix things, etc., in those
> cases where emacs uses yes-or-no-p , thank you!

Yup, this would be nice to have in y-or-n-p too.  Perhaps y-or-n-p should
accept 'y' and 'n' (and perhaps space and del) as valid answers, and
interpret other keystrokes normally?  Then one could switch buffers, fix
things, etc., and then come back to the minibuffer and type 'y' or 'n'.

-- Ashwin.