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.bugs Subject: bug#48249: 28.0.50; Regression: emacs confused about window configuration due to ido-mode and/or winner-mode Date: Thu, 06 May 2021 12:39:46 +0300 Message-ID: <83pmy4dwv1.fsf@gnu.org> References: <87zgx8wmew.fsf@secretsauce.net> <531453ddd62d1011193c@heytings.org> <831rakffuj.fsf@gnu.org> <531453ddd66aad05f4af@heytings.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14253"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 48249@debbugs.gnu.org, dima@secretsauce.net To: Gregory Heytings Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu May 06 11:41:11 2021 Return-path: Envelope-to: geb-bug-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 1leaVK-0003bQ-Ua for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 06 May 2021 11:41:10 +0200 Original-Received: from localhost ([::1]:40062 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1leaVK-0001vr-0d for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 06 May 2021 05:41:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42116) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1leaVC-0001uH-7d for bug-gnu-emacs@gnu.org; Thu, 06 May 2021 05:41:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:53817) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1leaVB-0005TY-Ue for bug-gnu-emacs@gnu.org; Thu, 06 May 2021 05:41:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1leaVB-0007jn-Qe for bug-gnu-emacs@gnu.org; Thu, 06 May 2021 05:41:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 06 May 2021 09:41:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 48249 X-GNU-PR-Package: emacs Original-Received: via spool by 48249-submit@debbugs.gnu.org id=B48249.162029400729718 (code B ref 48249); Thu, 06 May 2021 09:41:01 +0000 Original-Received: (at 48249) by debbugs.gnu.org; 6 May 2021 09:40:07 +0000 Original-Received: from localhost ([127.0.0.1]:37130 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1leaUJ-0007jG-71 for submit@debbugs.gnu.org; Thu, 06 May 2021 05:40:07 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:33394) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1leaUF-0007ig-Hw for 48249@debbugs.gnu.org; Thu, 06 May 2021 05:40:06 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:53100) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1leaUA-0004ig-5W; Thu, 06 May 2021 05:39:58 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:4556 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1leaU9-0003ty-QG; Thu, 06 May 2021 05:39:58 -0400 In-Reply-To: <531453ddd66aad05f4af@heytings.org> (message from Gregory Heytings on Thu, 06 May 2021 08:17:59 +0000) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:205785 Archived-At: > Date: Thu, 06 May 2021 08:17:59 +0000 > From: Gregory Heytings > cc: 48249@debbugs.gnu.org, dima@secretsauce.net > > > Significant changes in low-level infrastructure frequently cause a trail > > of unintended consequences that need to be fixed. > > When a low-level infrastructure has worked flawlessly for more than a > decade, making significant changes in it without making them conditional > to a run-time variable or a compilation option, until the new code is > "proven" enough, is unwise. First, a knob to control new code is not always possible, though I agree it is preferable when it's feasible. In this case, we do have a knob to control the new code, albeit not a knob that goes back to the previous behavior with 100% accuracy. It's possible that the OP should try flipping that option, maybe it will work around the problem (not that I think it's necessarily the solution). More generally, that's development for you; without risking such destabilization from time to time we can never afford significant improvements. The important question is: will the new-and-improved behavior be useful or won't it? > > If you think what we saw till now as result of that changeset is a > > catastrophe, you just didn't see enough serious low-level changes in > > Emacs yet. > > Did other low-level changes in Emacs result in segfaults and several bug > reports of confused users each week? I'd hope not. Yes, of course. The introduction of bidirectional editing support during development of Emacs 24.1 comes to mind. Like I said: stick around some more, and you will see more examples. Emacs 28.1 is still many moons away. We will figure this out till then, don't worry.