From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Confused by y-or-n-p Date: Wed, 06 Jan 2021 17:17:50 +0200 Message-ID: <83czyi2ixt.fsf@gnu.org> 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> <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> <87im8f951f.fsf@gnus.org> <83lfdacapo.fsf@gnu.org> <8335zgd9xu.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21741"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rudalics@gmx.at, larsi@gnus.org, juri@linkov.net, drew.adams@oracle.com, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jan 06 16:19:00 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 1kxAaR-0005YS-UM for ged-emacs-devel@m.gmane-mx.org; Wed, 06 Jan 2021 16:18:59 +0100 Original-Received: from localhost ([::1]:46722 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kxAaQ-000169-Ux for ged-emacs-devel@m.gmane-mx.org; Wed, 06 Jan 2021 10:18:58 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60712) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kxAZT-00006c-G4 for emacs-devel@gnu.org; Wed, 06 Jan 2021 10:17:59 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:34065) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kxAZT-00068L-7P; Wed, 06 Jan 2021 10:17:59 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:3761 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kxAZL-0005au-4I; Wed, 06 Jan 2021 10:17:51 -0500 In-Reply-To: (message from Richard Stallman on Wed, 06 Jan 2021 00:01:20 -0500) 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:262596 Archived-At: > From: Richard Stallman > Cc: rudalics@gmx.at, larsi@gnus.org, emacs-devel@gnu.org, > drew.adams@oracle.com, juri@linkov.net > Date: Wed, 06 Jan 2021 00:01:20 -0500 > > > > My proposal will help with that problem too. Instead of waiting for a > > > resolution of the dispute, we should install the change with a user > > > option variable to enable the new behavior. > > > That is already happening where the change seems to be controversial > > or a too radical departure from long-time behavior. > > That's good. But it suggests that the spectre of "interminable > dispute" has been exaggerated. If people are getting tired of > a dispute, they will get behind the solution of "install it with > an option" and we will go ahead with that. You are forgetting the cases where such a variable is inappropriate, for example if the person who proposes the change thinks the change fixes a bug, or when such a variable is not feasible. Besides, no one can be sure that people who get tired will implement such a variable to stop the dispute. They are quite likely to give up on the change instead.