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: Sun, 27 Dec 2020 18:25:08 +0200 Organization: LINKOV.NET Message-ID: <87k0t38g1z.fsf@mail.linkov.net> References: <834kkcr1eo.fsf@gnu.org> <43b24209-fa65-0e26-7cbd-f99175a7ffd8@gmx.at> <87wnx7j5is.fsf@mail.linkov.net> <83im8qnyca.fsf@gnu.org> <83bleinmse.fsf@gnu.org> <56435592-d2d0-5fb6-977f-01e1931da835@gmx.at> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25904"; 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: eliz@gnu.org, rms@gnu.org, emacs-devel@gnu.org To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 27 17:28:25 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 1ktYu9-0006Yp-DY for ged-emacs-devel@m.gmane-mx.org; Sun, 27 Dec 2020 17:28:25 +0100 Original-Received: from localhost ([::1]:45430 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ktYu8-0005q6-GW for ged-emacs-devel@m.gmane-mx.org; Sun, 27 Dec 2020 11:28:24 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41154) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ktYrb-00042V-0I for emacs-devel@gnu.org; Sun, 27 Dec 2020 11:25:47 -0500 Original-Received: from relay10.mail.gandi.net ([217.70.178.230]:45795) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ktYrZ-0005kS-7x; Sun, 27 Dec 2020 11:25:46 -0500 Original-Received: from mail.gandi.net (m91-129-99-98.cust.tele2.ee [91.129.99.98]) (Authenticated sender: juri@linkov.net) by relay10.mail.gandi.net (Postfix) with ESMTPSA id A96C8240004; Sun, 27 Dec 2020 16:25:40 +0000 (UTC) In-Reply-To: (martin rudalics's message of "Sat, 26 Dec 2020 14:41:21 +0100") Received-SPF: pass client-ip=217.70.178.230; envelope-from=juri@linkov.net; helo=relay10.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, RCVD_IN_MSPIKE_H2=-0.001, 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:261905 Archived-At: > The most simple approach to get the old behavior back is to restore the > old code for 'y-or-n-p', rename it to something like 'y-or-n-p-old' and > call it when an option like `y-or-n-p-use-old' is non-nil. This is exactly what we recently did for the function 'read-char-choice'. Instead of changing its long-standing implementation that uses 'read-key', we left it unchanged, and only changed its caller to rely on a different function that uses the minibuffer to read a character. The same way we could add a function with old implementation of 'y-or-n-p', and depending on an option use either of them. So two new options are needed: to select an implementation of y-or-n-p and and also an option to choose either to use yes-or-no-p or y-or-n-p with shorter answers. Or maybe just one variable with three choices: long answers with yes-or-no-p, short answers with read-key, short answers with the minibuffer.