From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Confused by y-or-n-p Date: Mon, 28 Dec 2020 00:26:00 -0500 Message-ID: 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> <87k0t38g1z.fsf@mail.linkov.net> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30700"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rudalics@gmx.at, eliz@gnu.org, emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Dec 28 06:27:14 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 1ktl3p-0007fs-T6 for ged-emacs-devel@m.gmane-mx.org; Mon, 28 Dec 2020 06:27:13 +0100 Original-Received: from localhost ([::1]:42218 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ktl3o-000284-Vs for ged-emacs-devel@m.gmane-mx.org; Mon, 28 Dec 2020 00:27:13 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34634) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ktl2u-0001Ik-Q7 for emacs-devel@gnu.org; Mon, 28 Dec 2020 00:26:16 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:35003) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ktl2u-0003EQ-3l; Mon, 28 Dec 2020 00:26:16 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1ktl2e-00005r-Qn; Mon, 28 Dec 2020 00:26:04 -0500 In-Reply-To: <87k0t38g1z.fsf@mail.linkov.net> (message from Juri Linkov on Sun, 27 Dec 2020 18:25:08 +0200) 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:261977 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > 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 That is the right approach, but there are other places where Emacs asks for a one-character answer and I'd like them to go back to the old behavior also. Perhaps you need to do this at the level of read-char-choice. and also an option > to choose either to use yes-or-no-p or y-or-n-p with shorter answers. If someone wants that option I see no harm in providing it. Did anyone actually ask for it, or was it proposed simply in the search for more alternative behaviors? > 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. Ok, provided it is for all the one-character answers, not solely for y-or-n-p. -- Dr Richard Stallman Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)