bug#66326: 29.1.50; There should be a way to promote warnings to errors

[Eli Zaretskii <eliz@gnu.org>]

> From: Spencer Baugh <sbaugh@janestreet.com>
> Cc: Stefan Kangas <stefankangas@gmail.com>,  Eli Zaretskii <eliz@gnu.org>,
>    66326@debbugs.gnu.org
> Date: Fri, 10 Nov 2023 16:40:14 -0500
> 
> I just ran into a situation like this yet again.  Again, there was a
> stray warning on startup (something about "Symbol’s value as variable is
> void", definitely concerning)

The text you quote is not a warning, it's an error.  --debug-init
should have taken care of debugging it, AFAIU.

And let me reiterate what I said previously (and you quoted here):

>>> More generally, I'm worried by the tendency of people to submit
>>> patches for Emacs as soon as they find something they think is missing
>>> in Emacs that they need for some one-time job.  Emacs is not supposed
>>> to be a huge heap of random features that someone at some time found
>>> useful for some random job.  Emacs is Free Software: you can easily
>>> implement this stuff in your local copy and use it as much as you
>>> want; no need to add that to the Emacs core, unless there's a real
>>> need for it expressed by enough people, and no better solutions in
>>> hand.  I do this for my local jobs all the time.

I still don't think I see why this particular issue should be
everyone's problem, not just something you solve locally, if you
indeed bump frequently into these issues.