From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@catern.com>
Cc: sbaugh@janestreet.com, 66326@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#66326: 29.1.50; There should be a way to promote warnings to errors
Date: Sat, 11 Nov 2023 16:51:27 +0200 [thread overview]
Message-ID: <834jhswdg0.fsf@gnu.org> (raw)
In-Reply-To: <87a5rk8igj.fsf@catern.com> (message from Spencer Baugh on Sat, 11 Nov 2023 14:37:03 +0000 (UTC))
> From: Spencer Baugh <sbaugh@catern.com>
> Date: Sat, 11 Nov 2023 14:37:03 +0000 (UTC)
> Cc: Spencer Baugh <sbaugh@janestreet.com>, 66326@debbugs.gnu.org,
> stefankangas@gmail.com
>
> 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.
Then you need to find that code, and Bob's your uncle.
I see no need to add complications to Emacs based on such use cases.
We cannot be expected to have a ready solution for every possible
Emacs-related calamity.
prev parent reply other threads:[~2023-11-11 14:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 16:38 bug#66326: 29.1.50; There should be a way to promote warnings to errors Spencer Baugh
2023-10-03 18:39 ` Spencer Baugh
2023-10-03 18:57 ` Eli Zaretskii
2023-10-03 19:16 ` sbaugh
2023-10-04 5:59 ` Eli Zaretskii
2023-10-04 12:20 ` Spencer Baugh
2023-10-14 7:27 ` Eli Zaretskii
2023-10-14 22:25 ` sbaugh
2023-10-15 5:45 ` Eli Zaretskii
2023-10-16 19:26 ` Spencer Baugh
2023-10-19 12:13 ` Eli Zaretskii
2023-10-19 14:50 ` Spencer Baugh
2023-10-19 15:07 ` Eli Zaretskii
2023-10-19 15:18 ` Spencer Baugh
2023-10-19 15:42 ` Eli Zaretskii
2023-10-19 16:15 ` Spencer Baugh
2023-10-20 7:20 ` Eli Zaretskii
2023-10-21 9:12 ` Stefan Kangas
2023-10-21 13:43 ` sbaugh
2023-11-10 21:40 ` Spencer Baugh
2023-11-11 7:02 ` Eli Zaretskii
2023-11-11 14:37 ` Spencer Baugh
2023-11-11 14:51 ` Eli Zaretskii [this message]
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=834jhswdg0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66326@debbugs.gnu.org \
--cc=sbaugh@catern.com \
--cc=sbaugh@janestreet.com \
--cc=stefankangas@gmail.com \
/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.