From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: Another Emacs incompatibilty Date: Mon, 17 Aug 2020 16:42:00 -0400 Message-ID: References: <86r1s648dc.fsf@shell.gmplib.org> <86wo1xz4lt.fsf@shell.gmplib.org> <83imdhgsqo.fsf@gnu.org> <86blj9xc2z.fsf@shell.gmplib.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19439"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Cancel-Lock: sha1:iaN9cPdEapmgx5SkEkce/pfu2x0= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Mon Aug 17 22:42:39 2020 Return-path: Envelope-to: geh-help-gnu-emacs@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 1k7lxn-0004yq-6q for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 17 Aug 2020 22:42:39 +0200 Original-Received: from localhost ([::1]:43332 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k7lxm-0004te-8H for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 17 Aug 2020 16:42:38 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44436) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k7lxL-0004tX-C8 for help-gnu-emacs@gnu.org; Mon, 17 Aug 2020 16:42:11 -0400 Original-Received: from static.214.254.202.116.clients.your-server.de ([116.202.254.214]:55424 helo=ciao.gmane.io) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k7lxJ-00023I-Un for help-gnu-emacs@gnu.org; Mon, 17 Aug 2020 16:42:11 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1k7lxF-0004Io-Ra for help-gnu-emacs@gnu.org; Mon, 17 Aug 2020 22:42:05 +0200 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=geh-help-gnu-emacs@m.gmane-mx.org; helo=ciao.gmane.io X-detected-operating-system: by eggs.gnu.org: First seen = 2020/08/17 10:21:47 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -8 X-Spam_score: -0.9 X-Spam_bar: / X-Spam_report: (-0.9 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:123698 Archived-At: > Mark a region, immediately press e.g. "A". The region is zapped and > replaced by an A. > > That used to insert an A at the insert point since TECO emacs until a > few releases back. Still does for me in a vanilla Emacs. Maybe it's something in your config? > In any case, whenever a backward-incompatible change happens, there's > usually a way, called out in NEWS, to get back old behavior. > How about keeping the accepted interface and document in NEWS how to > make it work in a new, incompatible way? That's what we do for most new features. But sometimes the annoyance for N users of having to disable a "feature" is eclipsed by the expected benefit for M users getting this new "feature" without having to figure that they want it nor how to get it. For any change to Emacs (new feature, change to defaults, bug fix, you name it), one can easily come up with some scenario where the change results in an undesired result [ the credibility/likelihood of the scenario may vary widely, of course ]. So the only really safe way to avoid introducing new problems is to leave the code 100% unchanged. Stefan