From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Konstantin Kharlamov Newsgroups: gmane.emacs.bugs Subject: bug#60854: [PATCH] Make warnings show a "warning" emoji instead of a stop-sign Date: Fri, 31 Mar 2023 10:48:12 +0300 Message-ID: References: <20230211084559.516124-1-Hi-Angel@yandex.ru> <83h6vsjxpe.fsf@gnu.org> <1214753ab8b9b72bb2dbbeb4113e67ab0b088167.camel@yandex.ru> <9f05f1a05b9d8f1a496aed84bf44b039ac7bb662.camel@yandex.ru> <83355l4g7w.fsf@gnu.org> <7378ade3da2c8965c410b4135db74736d42cd4b2.camel@yandex.ru> <83pm8p2yej.fsf@gnu.org> 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="28744"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Evolution 3.46.4 Cc: 60854@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Mar 31 09:49:15 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1pi9Va-0007Kl-F9 for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 31 Mar 2023 09:49:14 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pi9VQ-0005u7-U6; Fri, 31 Mar 2023 03:49:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pi9VO-0005tk-OU for bug-gnu-emacs@gnu.org; Fri, 31 Mar 2023 03:49:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pi9VO-0000EZ-G6 for bug-gnu-emacs@gnu.org; Fri, 31 Mar 2023 03:49:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pi9VO-0004zV-C5 for bug-gnu-emacs@gnu.org; Fri, 31 Mar 2023 03:49:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Konstantin Kharlamov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 31 Mar 2023 07:49:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 60854 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 60854-submit@debbugs.gnu.org id=B60854.168024889819051 (code B ref 60854); Fri, 31 Mar 2023 07:49:02 +0000 Original-Received: (at 60854) by debbugs.gnu.org; 31 Mar 2023 07:48:18 +0000 Original-Received: from localhost ([127.0.0.1]:60298 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pi9Ug-0004xA-84 for submit@debbugs.gnu.org; Fri, 31 Mar 2023 03:48:18 -0400 Original-Received: from forward502b.mail.yandex.net ([178.154.239.146]:53920) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pi9Ud-0004wd-4E for 60854@debbugs.gnu.org; Fri, 31 Mar 2023 03:48:16 -0400 Original-Received: from mail-nwsmtp-smtp-production-main-60.sas.yp-c.yandex.net (mail-nwsmtp-smtp-production-main-60.sas.yp-c.yandex.net [IPv6:2a02:6b8:c08:8212:0:640:cefe:0]) by forward502b.mail.yandex.net (Yandex) with ESMTP id 2ACCF5F1C7; Fri, 31 Mar 2023 10:48:13 +0300 (MSK) Original-Received: by mail-nwsmtp-smtp-production-main-60.sas.yp-c.yandex.net (smtp/Yandex) with ESMTPSA id CmETWaADcmI0-OZSMGIs4; Fri, 31 Mar 2023 10:48:12 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1680248892; bh=CW/lMr7OTBsuE5f74zaMey1u82rLjY6M3A3fxEusw9M=; h=References:Date:In-Reply-To:Cc:To:From:Subject:Message-ID; b=motHVWnsaEzBvbbsupFtafreKL0mnc9vG22BW1dD1lwv0AbrkENSeIeMKcGG6UnVf JuZQnICt4ui7ueyNDl6Li3LXLxdCqjlmJhqtwEhk3WIzrUEmDtRldRukKF+3LRyRXM AgQuGjulURJSYniXhlbeOctLREWgMkxoB1OmEWrE= Authentication-Results: mail-nwsmtp-smtp-production-main-60.sas.yp-c.yandex.net; dkim=pass header.i=@yandex.ru In-Reply-To: <83pm8p2yej.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:258982 Archived-At: On Fri, 2023-03-31 at 10:05 +0300, Eli Zaretskii wrote: > > From: Konstantin Kharlamov > > Cc: 60854@debbugs.gnu.org > > Date: Fri, 31 Mar 2023 09:26:38 +0300 > >=20 > > Actually, scratch that, it's even worse. You see: the byte-compiled > > packages are natively-compiled on demand, i.e. on the first use. So, > > suppose you updated your (M)ELPA packages. What happens is that you > > get a bunch of warnings for packages that were loaded immediately, > > which is not all of them. During Emacs use later, as you open new > > files that weren't opened during the update thus triggering the > > according modes to load, you will get more and more new warnings. >=20 > Emacs 28 with native-compilation was released a year ago.=C2=A0 MELPA > packages should have adapted to that long ago, by fixing the problems > which cause those warnings.=C2=A0 My suggestion is to file issues with th= e > respective developers and pinging them until they resolve this.=C2=A0 In > almost all cases, these warnings are due to missing 'require's or > other similar omissions.=C2=A0 There's no justification for these problem= s > to exist in the year 2023. FWIW, I co-maintain a color-identifiers mode on github, and I have occasion= ally introduced new native-comp warnings (about a variable being referred in a function before its `defvar`). This happens because you debug and test ELis= p code without it being compiled at all. Then later after everything seems to work, you test that byte-compilation produces no warnings. But at that poin= t you don't know there isn't any warnings from native-comp, so you also need to l= oad the byte-compiled file, which is easy to forget. That, and given that some modes in (M)Elpa may be unmaintained =E2=80=94 I = don't see native-comp warnings go away any time soon. I do sympathise your wish to improve (M)Elpa packages. But the discussed pr= oblem with the wrong emoji shown is not a problem of those modes, it's the Emacs problem. When you see "BIG RED ERROR" for a harmless warning from a `foo-mo= de`, the bad experience is not related to `foo-mode` but to Emacs that disturbs = a user for no reason. Simply changing emoji would still show interested users there is a problem = with their mode that they can fix, but at the same time would avoid attributing negative experience to Emacs per se.