From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: native-comp *Warnings* buffer Date: Sun, 16 May 2021 23:23:34 -0400 Message-ID: References: <87k0o2z9pr.fsf@ericabrahamsen.net> <83y2chzvxw.fsf@gnu.org> <87czttxquo.fsf@ericabrahamsen.net> <87y2cfwbz5.fsf@ericabrahamsen.net> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38073"; mail-complaints-to="usenet@ciao.gmane.io" Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Eric Abrahamsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon May 17 05:24:26 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 1liTrl-0009jL-M7 for ged-emacs-devel@m.gmane-mx.org; Mon, 17 May 2021 05:24:25 +0200 Original-Received: from localhost ([::1]:36596 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1liTrk-0006vY-DB for ged-emacs-devel@m.gmane-mx.org; Sun, 16 May 2021 23:24:24 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57852) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1liTqy-0006H6-21 for emacs-devel@gnu.org; Sun, 16 May 2021 23:23:36 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:53102) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1liTqx-0004Kz-3y; Sun, 16 May 2021 23:23:35 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1liTqw-0007I5-Dx; Sun, 16 May 2021 23:23:34 -0400 In-Reply-To: <87y2cfwbz5.fsf@ericabrahamsen.net> (message from Eric Abrahamsen on Sat, 15 May 2021 21:15:26 -0700) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:269384 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > This wouldn't affect the actual compilation at all. It could affect > whether the user sees the warnings or not, if we default to not popping > up the *Warnings* buffer. They might still go looking for the buffer, or > stumble upon it by accident, though. Yes, that's exactly the issue. If you were going to have a compilation of foo.el based on some explicit request, and therefore see its warnings then, anything that compiles it by anticipation and does not show you its warnings could cause that explicit request NOT to compile it (because it was compiled recently), and therefore you would never see its warnings. Most of the time this would not matter at all. However, on rare occasions it could cause a real problem. Perhaps even a serious one. So I think it is important to make sure this scenario -- suppressing a warning you would have been shown -- cannot happen. There are many ways to do that. My concern is simply that it be done, one way or another. -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)