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 *Warnings* buffer Date: Mon, 17 May 2021 09:16:28 +0300 Message-ID: <83tun1ubpf.fsf@gnu.org> References: <87k0o2z9pr.fsf@ericabrahamsen.net> <83y2chzvxw.fsf@gnu.org> <87czttxquo.fsf@ericabrahamsen.net> <87y2cfwbz5.fsf@ericabrahamsen.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25075"; mail-complaints-to="usenet@ciao.gmane.io" Cc: eric@ericabrahamsen.net, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon May 17 08:17:32 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 1liWZH-0006Fz-K1 for ged-emacs-devel@m.gmane-mx.org; Mon, 17 May 2021 08:17:31 +0200 Original-Received: from localhost ([::1]:40514 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1liWZF-0006QF-Og for ged-emacs-devel@m.gmane-mx.org; Mon, 17 May 2021 02:17:29 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57032) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1liWYL-0005iv-9e for emacs-devel@gnu.org; Mon, 17 May 2021 02:16:38 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:58454) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1liWYK-00010D-KD; Mon, 17 May 2021 02:16:32 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1107 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 1liWYC-0005lP-Sa; Mon, 17 May 2021 02:16:26 -0400 In-Reply-To: (message from Richard Stallman on Sun, 16 May 2021 23:23:34 -0400) 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:269392 Archived-At: > From: Richard Stallman > Date: Sun, 16 May 2021 23:23:34 -0400 > Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org > > 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. I don't think I understand the scenario you described. Could you perhaps describe it in simpler terms, like . user does A . Emacs does X and shows Y . user does B . emacs shows Z etc.? I'm asking because I'd like to figure out what we currently do in this situation, and how this discussion could affect that. Thanks.