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 11:45:46 -0500 Message-ID: References: <834kkcr1eo.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="24639"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Richard Stallman , 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 17:47:43 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 1ks7Id-0006Gg-F5 for ged-emacs-devel@m.gmane-mx.org; Wed, 23 Dec 2020 17:47:43 +0100 Original-Received: from localhost ([::1]:58256 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ks7Ic-0007Kq-Hl for ged-emacs-devel@m.gmane-mx.org; Wed, 23 Dec 2020 11:47:42 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38646) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ks7Gw-0006g6-C6 for emacs-devel@gnu.org; Wed, 23 Dec 2020 11:45:58 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:45679) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ks7Go-0004K4-Fo; Wed, 23 Dec 2020 11:45:51 -0500 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id F3F4A440615; Wed, 23 Dec 2020 11:45:48 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id D206D4405EF; Wed, 23 Dec 2020 11:45:47 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1608741947; bh=Dnm2Z9mNrGaUwM7C7Kri9Jm4BAQFvrzTljPpAf3X6bE=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=GhwPKqdMkyLmDA1FNFmPLcFN8TD0EJORhXSEuOKsAgMTjl94nlYo4pRn0rMxrxp3Y M3J/Hj78aChnGyD09EapKVAAkA+TXgH8wLo4WnEtIT1Qpq0PW4ZDnidKMxVm46keDY aEAMpnBDpJjPzVhV054SlpyiH8ZHDCJJ7AZg022mN0e2KSv6YR/cEtVoJpTDLnvewp 9lhx/VdBMuksi5Kl6idr6d/bQp3K1iBj7hX0F3Cmz5F7oFpaxQu6i5BN45PeMjioBC AHp+QJubwTn4L9RN0qAQA+1rUdk7i9Aw6KHkEmk1yq0RXJ2IwsIUxyz1d+Ued3TMTj /vCvn7QNyAU/A== Original-Received: from alfajor (69-165-136-52.dsl.teksavvy.com [69.165.136.52]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 97AD8120193; Wed, 23 Dec 2020 11:45:47 -0500 (EST) In-Reply-To: <834kkcr1eo.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 23 Dec 2020 17:24:15 +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:261617 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? Stefan