From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48337@debbugs.gnu.org, alex.bennee@linaro.org, acm@muc.de
Subject: bug#48337: Fwd: 28.0.50; Emacs crashing randomly (possibly minibuffer activity related)
Date: Fri, 14 May 2021 17:31:12 +0000 [thread overview]
Message-ID: <425cd7715b1381e29e4c@heytings.org> (raw)
In-Reply-To: <83r1i9xpvk.fsf@gnu.org>
>> As I said to Eli a week ago or so: "So far I haven't seen a single
>> concrete example that demonstrates that this feature is either (a)
>> necessary in some circumstances (as was bidirectional editing support),
>> or (b) not necessary but at least useful in some circumstances." Does
>> anyone have such a concrete example? I'm all ears.
>>
>> It seems to me that the only benefit of this feature is a slightly
>> different minibuffer behavior, that some users may perhaps find more
>> convenient, as would be, for example, the possibility to display the
>> minibuffer at the top of the frames. Adding such a feature should not
>> make Emacs 28 backward-incompatible in any way.
>>
>> This experiment started in a bad way: its purpose was to fix a supposed
>> bug, which, as it turned out, was not a bug at all, but the result of a
>> misunderstanding, namely that isearch uses the echo area and not the
>> minibuffer. From then on, more and more changes were added to Emacs.
>
> We are a diverse group of people with different interests in Emacs
> development, each one scratching the itches that we have, which aren't
> necessarily itches for others. We should therefore all of us respect
> the interests and motivations of others, even if they scratch itches
> that don't look like itches to us.
>
> In this case, you have repeatedly stated your opposition to this change,
> and nothing positive can be expected from expressing that opposition one
> more time. Can you please calm down and let Alan fix whatever breakage
> he caused?
>
I'm very calm. Indeed I opposed this change, from day one, as much as,
and with the same energy as you opposed the change of the TAB key in xref
in bug#44611 for example.
I will continue to do so until someone explains why this change is a
"significant improvement" as you said, so significant that it's suddenly
okay to introduce backward-incompatible changes in a central UI element of
Emacs. IOW, the "something positive" that can be expected from that
opposition is an answer to that question.
next prev parent reply other threads:[~2021-05-14 17:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87tunasd2u.fsf@linaro.org>
2021-05-10 19:30 ` bug#48337: Fwd: 28.0.50; Emacs crashing randomly (possibly minibuffer activity related) Alex Bennée
2021-05-10 19:34 ` bug#48337: Alex Bennée
2021-05-11 2:24 ` bug#48337: Fwd: 28.0.50; Emacs crashing randomly (possibly minibuffer activity related) Eli Zaretskii
2021-05-11 6:51 ` Alex Bennée
2021-05-11 8:23 ` Alex Bennée
2021-05-11 8:54 ` Alex Bennée
2021-05-11 12:21 ` Eli Zaretskii
2021-05-11 12:54 ` Alex Bennée
2021-05-11 13:42 ` Eli Zaretskii
2021-05-11 13:47 ` Eli Zaretskii
2021-05-11 19:45 ` Alan Mackenzie
2021-05-11 19:55 ` Eli Zaretskii
2021-05-12 18:54 ` Alan Mackenzie
2021-05-13 7:54 ` martin rudalics
2021-05-13 9:52 ` Alan Mackenzie
2021-05-13 11:54 ` Alan Mackenzie
2021-05-13 12:09 ` Alan Mackenzie
2021-05-14 15:20 ` Gregory Heytings
2021-05-14 16:05 ` Eli Zaretskii
2021-05-14 17:31 ` Gregory Heytings [this message]
2021-05-14 18:19 ` Eli Zaretskii
2021-05-15 9:45 ` Gregory Heytings
2021-05-11 20:14 ` Alan Mackenzie
2021-05-11 22:07 ` Alex Bennée
2021-05-14 16:31 ` Alan Mackenzie
2021-05-14 16:52 ` Alex Bennée
2021-05-14 18:40 ` Alan Mackenzie
2021-05-14 22:35 ` Alex Bennée
2021-05-15 12:00 ` Alan Mackenzie
2021-05-16 14:24 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=425cd7715b1381e29e4c@heytings.org \
--to=gregory@heytings.org \
--cc=48337@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=alex.bennee@linaro.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.