From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.devel Subject: Re: native-comp *Warnings* buffer Date: Fri, 14 May 2021 09:54:02 -0700 Message-ID: <2610F4DF-31BD-4E41-BCDE-BA12F8CB388D@ericabrahamsen.net> References: <87k0o2z9pr.fsf@ericabrahamsen.net> <83y2chzvxw.fsf@gnu.org> <87czttxquo.fsf@ericabrahamsen.net> <9FD44165-1C86-49C7-9B9A-57E281E546D6@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34647"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: K-9 Mail for Android Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri May 14 19:38:25 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 1lhblY-0008nz-R3 for ged-emacs-devel@m.gmane-mx.org; Fri, 14 May 2021 19:38:24 +0200 Original-Received: from localhost ([::1]:38674 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lhblX-00079E-O1 for ged-emacs-devel@m.gmane-mx.org; Fri, 14 May 2021 13:38:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59592) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lhb4j-0005SV-Bg for emacs-devel@gnu.org; Fri, 14 May 2021 12:54:09 -0400 Original-Received: from ericabrahamsen.net ([52.70.2.18]:49240 helo=mail.ericabrahamsen.net) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lhb4h-0001Mg-EK for emacs-devel@gnu.org; Fri, 14 May 2021 12:54:09 -0400 Original-Received: from [IPv6:2607:fb90:b283:83af:aeeb:ea91:62cb:c257] (unknown [172.56.42.68]) (Authenticated sender: eric@ericabrahamsen.net) by mail.ericabrahamsen.net (Postfix) with ESMTPSA id 3AD68FED1B; Fri, 14 May 2021 16:54:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericabrahamsen.net; s=mail; t=1621011245; bh=nOOYsLwHekjwvXJjh+pAtn/CL1ljl7FfHyK3oySCeeI=; h=Date:In-Reply-To:References:Subject:To:CC:From:From; b=jtQnylV4CkPLOV66KGxzQRjsB9Wt4Ex5Icm37Pz466bW0IJYVJvfAJOhXwW1hAKpn D69Xv4etAzmWhNFSlqxjHo3rHzLxqSkaljKhKFRdde3aGZ5v3+r3+XP2baVgOkEZPe oj2ycI/s1L/AXTHiHlxCo2q8jQ49KW3GmXrd/3oU= In-Reply-To: <9FD44165-1C86-49C7-9B9A-57E281E546D6@ericabrahamsen.net> Received-SPF: pass client-ip=52.70.2.18; envelope-from=eric@ericabrahamsen.net; helo=mail.ericabrahamsen.net X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:269289 Archived-At: On May 14, 2021 9:46:41 AM PDT, Eric Abrahamsen wrote: > > >On May 14, 2021 9:23:50 AM PDT, Stefan Monnier > wrote: >>> I guess usage=2E I only see the *Compilation* buffer when I've >>> done something to ask for it (updating packages, etc), and it's over >>> relatively quickly=2E These warnings went on for many long minutes, at >>> random intervals=2E I was trying to work in two side-by-side buffers, >>and >>> it kept stealing the other one -- I even switched frames once the >>> *Warnings* buffer was open, but it followed me to the new frame=2E >> >>I think "stealth" compilation performed opportunistically in the >>background should indeed not display any warnings (by default)=2E >> >>> I could do a patch for that, but the existing mechanisms *are* >pretty >>> thorough: big prominent buttons that do exactly what they promise to >>do >>> (I'm a bit embarrassed I didn't just read the instructions)=2E >> >>Don't those buttons also suppress the warnings for the normal >>(non-async, non-native) compilation case? If so, we should be careful >>not to encourage the users to do that when they're only annoyed by the >>async warnings=2E > >The buttons will add '(comp) to the list of suppressed warnings, so no >warnings with that tag would ever be popped-up, in any context=2E I'm not >sure what else uses that tag (I'm on my phone right now) but yes, that >might be a little drastic=2E If anyone else does use 'comp, we could have comp=2Eel use '(comp async), = which seems nicely targeted=2E