From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Confused by y-or-n-p Date: Thu, 24 Dec 2020 22:47:07 +0200 Organization: LINKOV.NET Message-ID: <87wnx7j5is.fsf@mail.linkov.net> References: <834kkcr1eo.fsf@gnu.org> <43b24209-fa65-0e26-7cbd-f99175a7ffd8@gmx.at> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28169"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) Cc: Eli Zaretskii , Richard Stallman , emacs-devel@gnu.org To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Dec 24 21:50:01 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 1ksXYe-0007CW-Qu for ged-emacs-devel@m.gmane-mx.org; Thu, 24 Dec 2020 21:50:00 +0100 Original-Received: from localhost ([::1]:38122 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ksXYd-0002s9-Td for ged-emacs-devel@m.gmane-mx.org; Thu, 24 Dec 2020 15:49:59 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46584) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ksXXi-0002Oe-FC for emacs-devel@gnu.org; Thu, 24 Dec 2020 15:49:02 -0500 Original-Received: from relay9-d.mail.gandi.net ([217.70.183.199]:52723) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ksXXe-0002MY-P5; Thu, 24 Dec 2020 15:49:01 -0500 X-Originating-IP: 91.129.99.98 Original-Received: from mail.gandi.net (m91-129-99-98.cust.tele2.ee [91.129.99.98]) (Authenticated sender: juri@linkov.net) by relay9-d.mail.gandi.net (Postfix) with ESMTPSA id D30ECFF805; Thu, 24 Dec 2020 20:48:53 +0000 (UTC) In-Reply-To: <43b24209-fa65-0e26-7cbd-f99175a7ffd8@gmx.at> (martin rudalics's message of "Thu, 24 Dec 2020 16:38:28 +0100") Received-SPF: pass client-ip=217.70.183.199; envelope-from=juri@linkov.net; helo=relay9-d.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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:261704 Archived-At: > In the Elisp manual we say that > > ‘yes-or-no-p’ requires more work from the user than ‘y-or-n-p’ and > is appropriate for more crucial decisions. > > Now while 'yes-or-no-p' implements what is sometimes called a "modeless" > or "non-modal" dialogue, our original 'y-or-n-p' implemented a "modal" > dialogue where the user had no other choice but to answer the question > immediately, possibly performing a few buffer scrolls in between. > > However, according to Wikipedia, modal dialogues are used > > "to command user awareness and to display emergency states" > > inherently contradicting what we say above. Maybe I'm the only one who > sees a contradiction here. Still I'd suggest to allow users to > separately choose for both, 'y-or-n-p' _and_ 'yes-or-no-p' dialogues, > whether they want Emacs to handle them in a modal or non-modal way. Indeed. Here is a possible way to make the minibuffer modal: (defun minibuffer-lock () (when (active-minibuffer-window) (select-window (active-minibuffer-window)))) (add-hook 'post-command-hook #'minibuffer-lock) > And while we're there we could also try to relieve some of our .emacs > files (mine included) of those > > (defalias 'yes-or-no-p 'y-or-n-p) > > by providing an option that accomplishes the necessary mapping. One complication is that currently yes-or-no-p is implemented in C, so using a new user option in it is not straightforward.