From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Confused by y-or-n-p Date: Wed, 23 Dec 2020 13:11:53 -0500 Message-ID: References: <834kkcr1eo.fsf@gnu.org> <83im8spgrz.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40525"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: rms@gnu.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Dec 23 19:13:26 2020 Return-path: 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 ) id 1ks8da-000AQo-46 for ged-emacs-devel@m.gmane-mx.org; Wed, 23 Dec 2020 19:13:26 +0100 Original-Received: from localhost ([::1]:48716 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ks8dZ-0006AA-6c for ged-emacs-devel@m.gmane-mx.org; Wed, 23 Dec 2020 13:13:25 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58274) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ks8cJ-0005HY-BT for emacs-devel@gnu.org; Wed, 23 Dec 2020 13:12:07 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:36477) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ks8cG-0003MK-Qe; Wed, 23 Dec 2020 13:12:06 -0500 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 1050E80A93; Wed, 23 Dec 2020 13:12:01 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id BF7558063C; Wed, 23 Dec 2020 13:11:59 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1608747119; bh=9DtZGLf1kgklN4Dr/mY7dmNmdxIYnFGmx6vXKX4vjX4=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=oG/8GbZeSllTrpu3f5uYt+A2x5Qsk3JEpqafsDOy3MxvKNHV7xJMBUqJ1pAngfbYC e5WnaK4BbhlDpwvsNWlbw/xa+tqkXMpJPllHMcD2O+wYrSL/4DCsDNIMa8cj/slOl8 0fT+PduOcXV0FtLC7qpauaqoPCL06fv50T9cX9bfnRVx9RhmXRBY0qGWdCQMKbtK4Z jid8OxjGZiirP+lMGghPHGGIaBp/URquPlgtupYwlXxqw9Wty7mZqTv7dQH2U14r1V B/Lepar7g8oIEKb7bMeTED9IBxIYqjwJ/KCqrp9gr+He5eYNxKTub+TWHYewsSF6fD Z1EeLnt9NrmnQ== Original-Received: from alfajor (69-165-136-52.dsl.teksavvy.com [69.165.136.52]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 8A738120124; Wed, 23 Dec 2020 13:11:59 -0500 (EST) In-Reply-To: <83im8spgrz.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 23 Dec 2020 19:35:12 +0200") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:261631 Archived-At: >> > 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. >> >> I wonder what makes `y-or-n-p` special in this respect. >> IOW, I think the answer is "yes, it would make sense" but I also think >> this option should apply to other cases that `y-or-n-p`. >> >> Maybe it could/should even apply to most uses of the minibuffer? > > Could be. However, y-or-n-p is somewhat special, in that it allowed > only very restricted set of things to type. By contrast > read-from-minibuffer always allowed switching out of the minibuffer. So you're saying the only reason to treat `y-or-n-p` differently is to avoid surprising old users? Fair enough, but IIRC `y-or-n-p` is not the only function we changed recently to use a minibuffer instead of an ad-hoc modal read-event loop, so I suspect we might want to apply this new option to those other functions as well. Stefan