[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#66326: 29.1.50; There should be a way to promote warnings to errors
|
From: |
Spencer Baugh |
|
Subject: |
bug#66326: 29.1.50; There should be a way to promote warnings to errors |
|
Date: |
Sat, 11 Nov 2023 14:37:03 +0000 (UTC) |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Eli Zaretskii <eliz@gnu.org> writes:
>> 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.
I know what the difference between an error and a warning is :) The
reason this text, which usually appears in errors, showed up as a
warning, was because some random code caught the error and turned it
into a warning.