From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: Confused by y-or-n-p Date: Thu, 07 Jan 2021 10:03:31 +0000 Message-ID: References: <834kkcr1eo.fsf@gnu.org> <87k0t38g1z.fsf@mail.linkov.net> <83czyvkts6.fsf@gnu.org> <87bleetirr.fsf@mail.linkov.net> <87y2hhri3n.fsf@mail.linkov.net> <83pn2tkfg8.fsf@gnu.org> <871rf7ippu.fsf@mail.linkov.net> <83a6trg6mc.fsf@gnu.org> <83mtxqcauz.fsf@gnu.org> <83turva0y2.fsf@gnu.org> Reply-To: Gregory Heytings Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10367"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Alpine 2.22 (NEB 394 2020-01-19) Cc: rms@gnu.org, emacs-devel@gnu.org, rudalics@gmx.at, Stefan Monnier , Eli Zaretskii , juri@linkov.net To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jan 07 11:06:02 2021 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 1kxSB8-0002a8-3p for ged-emacs-devel@m.gmane-mx.org; Thu, 07 Jan 2021 11:06:02 +0100 Original-Received: from localhost ([::1]:56382 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kxSB7-0002tN-5v for ged-emacs-devel@m.gmane-mx.org; Thu, 07 Jan 2021 05:06:01 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35632) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kxS9J-0001bu-8d for emacs-devel@gnu.org; Thu, 07 Jan 2021 05:04:09 -0500 Original-Received: from mx.sdf.org ([205.166.94.24]:49666) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kxS9D-00062M-9N; Thu, 07 Jan 2021 05:04:08 -0500 Original-Received: from sdf.org (IDENT:ghe@faeroes.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 107A3YmO013842 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Thu, 7 Jan 2021 10:03:34 GMT Original-Received: (from ghe@localhost) by sdf.org (8.15.2/8.12.8/Submit) id 107A49IJ003293; Thu, 7 Jan 2021 10:04:09 GMT In-Reply-To: Received-SPF: pass client-ip=205.166.94.24; envelope-from=ghe@sdf.org; helo=mx.sdf.org X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-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:262663 Archived-At: >> Perhaps I did not look at the right place, but I do not see such a rule >> or guideline in CONTRIBUTE or elsewhere. What do you (and others) >> think of the following: >> >> Any change that matters to end-users should have an entry in etc/NEWS. >> *In principle, any such change should, unless it is an added feature, >> either require setting a variable to be enabled, or be reversible by >> setting a variable.* > > I am against such a change, for the reasons given in my previous > message. > Which previous message? I don't see reasons against such a guideline in your previous message sent to this list. >>> Do you have any evidence to back up the claim that this has happened? >> >> It happened with y-or-n-p; it would not have happened with the above >> guideline. > > I don't think the second part of that sentence logically follows from > the first. > Just look at the entry for this change in NEWS.27 (and the read-char-from-minibuffer one), which does not explain how to revert it, unlike the three other entries in the "Minibuffer" section: *** 'y-or-n-p' now uses the minibuffer to read 'y' or 'n' answer. *** Some commands that previously used 'read-char-choice' now read a character using the minibuffer by 'read-char-from-minibuffer'. It seems to me that the "Any change that matters to end-users should have an entry in etc/NEWS" rule in CONTRIBUTE, which is already applied successfully, is also a good way to distinguish changes that are potentially controversial from the others, hence the proposal above.