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 05:35:42 +0200 Message-ID: <83mtxm3fg1.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> <83mtxqcauz.fsf@gnu.org> <83turva0y2.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="438"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rudalics@gmx.at, juri@linkov.net, rms@gnu.org, emacs-devel@gnu.org To: Gregory Heytings Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jan 06 04:37:34 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 1kwzde-000Ac8-4N for ged-emacs-devel@m.gmane-mx.org; Wed, 06 Jan 2021 04:37:34 +0100 Original-Received: from localhost ([::1]:43784 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kwzdd-000531-6T for ged-emacs-devel@m.gmane-mx.org; Tue, 05 Jan 2021 22:37:33 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44246) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kwzcd-0004KT-3x for emacs-devel@gnu.org; Tue, 05 Jan 2021 22:36:31 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:51424) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kwzca-0005QS-Lb; Tue, 05 Jan 2021 22:36:29 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:4432 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kwzbs-00019C-1i; Tue, 05 Jan 2021 22:35:47 -0500 In-Reply-To: (message from Gregory Heytings on Wed, 06 Jan 2021 00:14:21 +0000) 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:262561 Archived-At: > Date: Wed, 06 Jan 2021 00:14:21 +0000 > From: Gregory Heytings > cc: rms@gnu.org, rudalics@gmx.at, emacs-devel@gnu.org, juri@linkov.net > > > You are describing something that is already happening. In the vast > > majority of cases new features don't become the default, they are > > introduced as opt-in features and announced in NEWS. We consider making > > them the default after several releases, if and when people start asking > > us to enable a feature by default. > > I agree with you that this is already happening in the vast majority of > cases, so why would it be problematic to make this a rule, that in > principle any change to Emacs' behavior should provide a way to re-enable > the old behavior? Because the fact it's already happening means we already have the necessary rules, and adding more rules that restrict how we develop Emacs is an unnecessary overhead.