From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Eli Zaretskii <eliz@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Confused by y-or-n-p
Date: Wed, 23 Dec 2020 17:24:15 +0200
Message-ID: <834kkcr1eo.fsf@gnu.org>
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="16579"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: Richard Stallman <rms@gnu.org>
To: emacs-devel@gnu.org
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Dec 23 16:26:22 2020
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane-mx.org
Original-Received: from lists.gnu.org ([209.51.188.17])
	by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1ks61t-00049S-OU
	for ged-emacs-devel@m.gmane-mx.org; Wed, 23 Dec 2020 16:26:21 +0100
Original-Received: from localhost ([::1]:57776 helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1ks61s-0000r1-Q2
	for ged-emacs-devel@m.gmane-mx.org; Wed, 23 Dec 2020 10:26:20 -0500
Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49650)
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>) id 1ks60A-0008N2-UO
 for emacs-devel@gnu.org; Wed, 23 Dec 2020 10:24:34 -0500
Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:51615)
 by eggs.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <eliz@gnu.org>) id 1ks60A-0007kr-Lz
 for emacs-devel@gnu.org; Wed, 23 Dec 2020 10:24:34 -0500
Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2081
 helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.82) (envelope-from <eliz@gnu.org>)
 id 1ks602-0004Qb-A3; Wed, 23 Dec 2020 10:24:28 -0500
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org
Original-Sender: "Emacs-devel"
 <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
Xref: news.gmane.io gmane.emacs.devel:261600
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/261600>

The function y-or-n-p originally used to read only a small set of
character commands.  In Emacs 27.1 we changed it to use
read-from-minibuffer, which means users now can easily switch out of
the minibuffer while the question they were asked is still not
answered.

This could confuse some users, especially if they aren't used to
working with recursive minibuffers.  Richard tells me it happened to
him several times.

Would it make sense to add a user option to disallow switching from
the minibuffer in the middle of y-or-n-p?  Then people who get
confused by this could set it to avoid the confusion.