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 08:17:59 +0000 [thread overview]
Message-ID: <531453ddd66aad05f4af@heytings.org> (raw)
In-Reply-To: <831rakffuj.fsf@gnu.org>
>> I wonder how many more bug reports are needed before the lesson of that
>> failed experiment will finally be drawn.
>
> 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. That's what happened with native compilation
for example, or with Cairo, or... And this is all I asked when this
experiment started.
>
> 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.
next prev parent reply other threads:[~2021-05-06 8:17 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 [this message]
2021-05-06 9:39 ` Eli Zaretskii
2021-05-06 9:57 ` Gregory Heytings
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=531453ddd66aad05f4af@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).