[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Discuss new features/enhancements or large changes for users in emac
From: |
Eli Zaretskii |
Subject: |
Re: Discuss new features/enhancements or large changes for users in emacs-devel [was My resignation from Emacs development] |
Date: |
Tue, 03 Dec 2024 15:32:10 +0200 |
> From: Richard Stallman <rms@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Tue, 03 Dec 2024 02:25:43 -0500
>
> > Bug#73853 was not about language-design decisions, it was about
> > deprecating a macro.
>
> I can see two possible meanings for what "Bug#73853" refers
> to in that sentenbce:
>
> 1. The original bug report which started that thread in bug-gnu-emacs.
>
> 2. The discussion thread which started with that bug report.
It is both, actually.
> Could it be that (1) was about deprecating that macro,
> and (2) started off there by wandered into a discussion of
> choosing major modes for various programming languages?
No. This is a misunderstanding: bug#73853 has nothing to do with
choosing major modes. That bug was about and-let* and when-let*, and
was brought up here as an example of a discussion that should have
been taken to emacs-devel, because it (allegedly) was about the
language design of Emacs Lisp.
> While the discussion was about deprecating a macro, discussing it
> in a bu report ticket made sense.
>
> Once it changed to be about proposals for controlling major modes,
> someone should have moved it to emacs-devel.
It never did. Instead, someone in that discussion mentioned in
passing some aspects of language design related to the discussion.
That was a tangent that fortunately didn't deflect the discussion.
I think you confuse this with another bug, bug#69191. That one was
about remapping major modes from the get-go.