From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings 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 09:57:04 +0000 Message-ID: <531453ddd625bf0ea1b9@heytings.org> References: <87zgx8wmew.fsf@secretsauce.net> <531453ddd62d1011193c@heytings.org> <831rakffuj.fsf@gnu.org> <531453ddd66aad05f4af@heytings.org> <83pmy4dwv1.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28067"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 48249@debbugs.gnu.org, dima@secretsauce.net To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu May 06 11:58:57 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 1leamW-00078N-Uf for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 06 May 2021 11:58:56 +0200 Original-Received: from localhost ([::1]:57048 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1leamV-0002JU-VZ for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 06 May 2021 05:58:55 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47494) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1leale-0001uS-UV for bug-gnu-emacs@gnu.org; Thu, 06 May 2021 05:58:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:53855) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1leale-0000C6-N4 for bug-gnu-emacs@gnu.org; Thu, 06 May 2021 05:58:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1leale-0001dN-MM for bug-gnu-emacs@gnu.org; Thu, 06 May 2021 05:58:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 06 May 2021 09:58:02 +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.16202950296248 (code B ref 48249); Thu, 06 May 2021 09:58:02 +0000 Original-Received: (at 48249) by debbugs.gnu.org; 6 May 2021 09:57:09 +0000 Original-Received: from localhost ([127.0.0.1]:37164 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1leakn-0001ci-JE for submit@debbugs.gnu.org; Thu, 06 May 2021 05:57:09 -0400 Original-Received: from heytings.org ([95.142.160.155]:39966) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1leakk-0001cc-63 for 48249@debbugs.gnu.org; Thu, 06 May 2021 05:57:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20210101; t=1620295025; bh=WImsMFXLZDRz1NfE0HnNgKrK/2z0N8y2WF0TMTlJ/aU=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=vrD1ZCe7caJF0L4WdMJc7bV2QqA4ZgeulSbLIWacOKsnSwHBjq7MG9vkydEGnHU0G 73JEupr5+pQjNno/0hMYWgej9eACdZvWoEgNxQi7QLBDk97jTjXNqGURUoFUcrFWIU 7o2kPmiH6uuJKdPxgezCFuUwWac9eczH9dS7SqywfJslnxafPK2A9H9j95lRUnO9u5 /57IVKqBe/njDeoL7rRfBC56ciGh6zZxaq8igMYd5ElTZCV2rGhsfdIm4Wf4iUba3o 62jr6Fon41HExTA4LRxAe2hgJpYhu1Zygrirb+/R73hnSUuxNhEqZjjEPEx6SFaLC8 NN/R5uP8uxGhw== In-Reply-To: <83pmy4dwv1.fsf@gnu.org> 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:205793 Archived-At: >> 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. > It is _always_ possible. Whether through conditional compilation or through conditional code. > > 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). > Turning the knob doesn't work here, the bug occurs regardless of the value of that knob. Otherwise I would have mentioned that in my reply to Dima. > > 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? > Indeed perhaps the most important question here is: is this a "significant improvement"? IMO, the answer is clearly "no". Will this new behavior be "useful"? In this case I'd say "perhaps, for very few users, even though nobody requested it". But a marginal improvement that will benefit a few users is not worth taking the risk of unconditionally destabilizing old, time-proved code. > > Yes, of course. The introduction of bidirectional editing support > during development of Emacs 24.1 comes to mind. > That was, of course, a significant improvement that was worth taking the risk of destabilization.