From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: native-comp-async-report-warnings-errors default value Date: Tue, 07 Dec 2021 16:15:50 +0200 Message-ID: <835ys0zejt.fsf@gnu.org> References: <87h7dj7su7.fsf@gmail.com> <83r1cnlu6y.fsf@gnu.org> <87czo77rx7.fsf@gmail.com> <837dcmamt2.fsf@gnu.org> <83v90694ka.fsf@gnu.org> <83v901zdh6.fsf@gnu.org> <8735n4hmyn.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18036"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rpluim@gmail.com, stefankangas@gmail.com, emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Dec 07 15:16:52 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mubGz-0004KH-0i for ged-emacs-devel@m.gmane-mx.org; Tue, 07 Dec 2021 15:16:49 +0100 Original-Received: from localhost ([::1]:60766 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mubGx-0002O8-I9 for ged-emacs-devel@m.gmane-mx.org; Tue, 07 Dec 2021 09:16:47 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:51988) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mubG2-0001bb-3W for emacs-devel@gnu.org; Tue, 07 Dec 2021 09:15:50 -0500 Original-Received: from [2001:470:142:3::e] (port=42656 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mubG1-0002Ra-Ox; Tue, 07 Dec 2021 09:15:49 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=ZIy1fdmKDVCTAQr2haU1navgUwLqPoj+RJnXMaBC6Ow=; b=X9ig/ISS53T7 PV1CpCKxe96ALgLxa0iJiNcE7JpGU92nEsQqTC97H8BYSH+A/vTvfz55PNGhoNd+UaA1OWjPyLUI5 UiSd/f9MmqUfBK0z3lR9zl7cGz52desfE2G3pHbDe7ABrKakBwYuC61xjoZqJDnUHYjSGGO8RqeZ6 PWrstbNNbKkgEoXQgaTDLQpxVfbHC85J6eFagc2B/VbZm9go7KyxizpdKJDKALn+j4RpHeovl7uYb 174Gjq1H+UoQtN3Qla2TVNWWpVd0ONB6aBrfAiDBih1gsrlzlpI1+Ut4OAAVAmRtvf8oHVghEdR3S 478u6GkPcejh7o5TZo3cqA==; Original-Received: from [87.69.77.57] (port=4078 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mubG1-0008LX-II; Tue, 07 Dec 2021 09:15:49 -0500 In-Reply-To: <8735n4hmyn.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 07 Dec 2021 08:51:28 +0100) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:281251 Archived-At: > From: Lars Ingebrigtsen > Cc: Stefan Kangas , rpluim@gmail.com, > emacs-devel@gnu.org > Date: Tue, 07 Dec 2021 08:51:28 +0100 > > Eli Zaretskii writes: > > > I'd rather sustain a barrage of annoyed people who think these > > warnings are gratuitous than explain to someone why Emacs decided to > > shut up these warnings by default and thus prevented him/her from > > seeing some warning which, if seen in time, could avoid a crash or > > some other catastrophic result. > > In my opinion, it's not something we should be showing to users. It's > highly irregular that we do -- we didn't present users saying "emacs" > with all the compilation warnings from building Emacs in Emacs 27.2, but > that's (in effect) what we're doing now. > > Compilation warnings are for developers, not users, so builds that are > geared towards users (as pretests are) should have this switched off. If the user visits a Lisp file and clicks the Emacs Lisp->Byte Compile item on the menu bar, we do pop up the compilation log buffer with the warnings and errors, right? And if the user installs or upgrades a package from ELPA, and the package is byte-compiled, the messages from that are shown, right? So it sounds like we already show these messages to users, and this is just another such situation. Once we decided to have JIT native compilation (and IMO it wouldn't make sense to decide differently), we should also agree to this side effect of compiling code in the background.