unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48249@debbugs.gnu.org, dima@secretsauce.net
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	[thread overview]
Message-ID: <531453ddd625bf0ea1b9@heytings.org> (raw)
In-Reply-To: <83pmy4dwv1.fsf@gnu.org>


>> 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.





  reply	other threads:[~2021-05-06  9:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06  3:50 bug#48249: 28.0.50; Regression: emacs confused about window configuration due to ido-mode and/or winner-mode Dima Kogan
2021-05-06  7:30 ` Gregory Heytings
2021-05-06  8:04   ` Eli Zaretskii
2021-05-06  8:17     ` Gregory Heytings
2021-05-06  9:39       ` Eli Zaretskii
2021-05-06  9:57         ` Gregory Heytings [this message]
2021-05-06 10:15           ` Eli Zaretskii
2021-05-06 11:48             ` Gregory Heytings
2021-05-06 12:30 ` Basil L. Contovounesios
2021-05-06 12:39   ` Gregory Heytings
2021-05-06 13:25     ` Basil L. Contovounesios
2021-05-06 13:38       ` Gregory Heytings
2021-05-06 13:58         ` Gregory Heytings
2021-05-06 14:22         ` Basil L. Contovounesios
2021-05-06 14:49     ` Basil L. Contovounesios
2021-05-06 19:25   ` Alan Mackenzie
2021-05-07  9:49   ` Alan Mackenzie
2021-05-07 10:24     ` Basil L. Contovounesios
2021-05-07 12:02     ` Gregory Heytings
2021-05-07 12:43       ` Alan Mackenzie
2021-05-07 20:30     ` Dima Kogan
2021-05-08 12:30       ` Alan Mackenzie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=531453ddd625bf0ea1b9@heytings.org \
    --to=gregory@heytings.org \
    --cc=48249@debbugs.gnu.org \
    --cc=dima@secretsauce.net \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).