From: Eli Zaretskii <eliz@gnu.org>
To: sbaugh@catern.com
Cc: sbaugh@janestreet.com, 66326@debbugs.gnu.org
Subject: bug#66326: 29.1.50; There should be a way to promote warnings to errors
Date: Sun, 15 Oct 2023 08:45:36 +0300 [thread overview]
Message-ID: <83a5skqvzz.fsf@gnu.org> (raw)
In-Reply-To: <87o7h0yh7k.fsf@catern.com> (sbaugh@catern.com)
> From: sbaugh@catern.com
> Date: Sat, 14 Oct 2023 22:25:37 +0000 (UTC)
> Cc: Spencer Baugh <sbaugh@janestreet.com>, 66326@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Spencer Baugh <sbaugh@janestreet.com>
> >> Cc: sbaugh@catern.com, 66326@debbugs.gnu.org
> >> Date: Wed, 04 Oct 2023 08:20:49 -0400
> >>
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >> > And in this case, duplication is a lesser evil than reordering of
> >> > logic, since the chances of unintended consequences would be lower in
> >> > the former case.
> >>
> >> OK, how about this version then?
> >
> > This is much better, thanks. But it still fails to execute this part
> > right away:
> >
> > (if (not (or after-init-time noninteractive (daemonp)))
> > ;; Ensure warnings that happen early in the startup sequence
> > ;; are visible when startup completes (bug#20792).
> > (delay-warning type message level buffer-name)
> >
> > We must preserve this functionality, unaffected by these changes. The
> > patch you propose doesn't seem to guarantee that, at least not
> > clearly enough for my palate.
>
> Ah, actually that's deliberate.
If it's deliberate, it will have to come with an additional option to
enable it. I don't want users to have their startup aborted just
because they want some warning later on converted to an error.
Startup is a delicate process where signaling errors is not always a
good idea, and we delay warnings there for a good reason. Changing
this unconditionally is not acceptable.
> (And that's one of the motivations of this change: to make it easier to
> debug a warning that happens during startup, by turning it into an error
> that can be debug-init'd)
There's no difficulty in debugging a warning whatsoever, IME. It is a
serious exaggeration to claim that there's a significant problem here
that needs a solution. Nevertheless, I'm okay with people opting in
to shooting themselves in the foot, I just don't agree to doing that
without an explicit user's consent.
next prev parent reply other threads:[~2023-10-15 5:45 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a5skqvzz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66326@debbugs.gnu.org \
--cc=sbaugh@catern.com \
--cc=sbaugh@janestreet.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).