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, 04 Jan 2021 00:16:55 -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> <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> 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="1832"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rudalics@gmx.at, larsi@gnus.org, emacs-devel@gnu.org, drew.adams@oracle.com, juri@linkov.net To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jan 04 06:18:25 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 1kwIG9-0000NK-MV for ged-emacs-devel@m.gmane-mx.org; Mon, 04 Jan 2021 06:18:25 +0100 Original-Received: from localhost ([::1]:44044 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kwIG8-0004Hd-OY for ged-emacs-devel@m.gmane-mx.org; Mon, 04 Jan 2021 00:18:24 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45128) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kwIF8-0003Oq-Ba for emacs-devel@gnu.org; Mon, 04 Jan 2021 00:17:25 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:55315) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kwIF7-0006QB-JG; Mon, 04 Jan 2021 00:17:21 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1kwIEh-0005ZB-2g; Mon, 04 Jan 2021 00:16:57 -0500 In-Reply-To: <83lfdacapo.fsf@gnu.org> (message from Eli Zaretskii on Sun, 03 Jan 2021 17:16:19 +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:262393 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. ]]] > When this happens in a released version, the resistance is justifiably > stronger. But those cases should be (and are, IME) very rare. My point is that they are not so rare -- there is a systematic tendency for that to happen. I am proposing a systematic way to make them less likely, by helping people take notice that a UI change is being proposed, so they can object quickly. > situation is actually the exact opposite: changes are being discussed > "to death" and sometimes never implemented due to controversy. 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 bypasss the dispute. -- 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)