From unknown Sat Jun 14 03:54:44 2025 X-Loop: help-debbugs@gnu.org Subject: bug#44746: 28.0.50; [feature/native-comp] Noisy "*Warnings*" buffer shown on start Resent-From: Stefan Kangas Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 20 Nov 2020 00:51:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: report 44746 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: To: 44746@debbugs.gnu.org X-Debbugs-Original-To: bug-gnu-emacs@gnu.org Received: via spool by submit@debbugs.gnu.org id=B.160583341521235 (code B ref -1); Fri, 20 Nov 2020 00:51:02 +0000 Received: (at submit) by debbugs.gnu.org; 20 Nov 2020 00:50:15 +0000 Received: from localhost ([127.0.0.1]:41391 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kfucx-0005WR-5R for submit@debbugs.gnu.org; Thu, 19 Nov 2020 19:50:15 -0500 Received: from lists.gnu.org ([209.51.188.17]:44700) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kfucv-0005WJ-0R for submit@debbugs.gnu.org; Thu, 19 Nov 2020 19:50:13 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:34090) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kfucu-0003XI-NQ for bug-gnu-emacs@gnu.org; Thu, 19 Nov 2020 19:50:12 -0500 Received: from mail-ed1-f52.google.com ([209.85.208.52]:34443) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kfucs-0004ed-Sw for bug-gnu-emacs@gnu.org; Thu, 19 Nov 2020 19:50:12 -0500 Received: by mail-ed1-f52.google.com with SMTP id a15so7821179edy.1 for ; Thu, 19 Nov 2020 16:50:10 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:date:message-id:subject:to :content-transfer-encoding; bh=jKTDG9xYM9ifU/u7KFhyjOcso5TaFvGnj20pCxo1LNQ=; b=Aa8J68q+hLoVYhhsirWGtS71rFfuMUsbBjM6N16tsOUz5ovZLyEynCg/ERw/HEmmGC JzoFV3kLeb36jKwDfSEoubIUV6RJzZb1fU2UxXQjzDXuV9w4GE1R84aVldx7k5HAZUhm eDGfjmVvNKTYKedEJnQQpELPQuf6uGH2L1b+UBDDTk57xnM2zQE5cE17keMy4jfuzuZV XWyEa3qzaJPzuEa+NSgaVoFNEhnGi0i97lKpUOhj+J5C+dZmXAu6qMPCjG5jHoSVI1Tm Mlu54U5oBQVIDtLnCRiC8ltPKLD3aeyo7xmZdzf1Cq8psAPSNpcElRA65HmkXqU/5h2m 0xvA== X-Gm-Message-State: AOAM5316Mjy7OzOnPlljETfkwo1ovxLgNOpFoi18ymxqpxHvpG9xkOru a48dQOiXFIkcuwGsOLAMzyZhkXJzq36V7sH/I+I5F9KqwTE= X-Google-Smtp-Source: ABdhPJw4GQKUjdKbuQEv/rc/+lunqVjjaLIHtko3m0Q6DWPgSKLtSSYsohbVr3KOxn/NzySOP5kM3A52i3NnVqCmFTA= X-Received: by 2002:a50:9f61:: with SMTP id b88mr34656027edf.282.1605833409016; Thu, 19 Nov 2020 16:50:09 -0800 (PST) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Thu, 19 Nov 2020 16:50:08 -0800 From: Stefan Kangas MIME-Version: 1.0 Date: Thu, 19 Nov 2020 16:50:08 -0800 Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=209.85.208.52; envelope-from=stefankangas@gmail.com; helo=mail-ed1-f52.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-Spam-Score: 0.7 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.8 (-) Every time I start Emacs after recompilation or clearing cache, I see a "*Warnings*" buffer popup in a new window, filled with a large amount of warnings like these: Warning (comp): debian-ispell.el:229:17: Warning: assignment to free variable Disable showing Disable logging Warning (comp): debian-ispell.el:228:28: Warning: reference to free variable =E2=80=98really-hunspell=E2=80=99 Disable showing Disable logging Warning (comp): debian-ispell.el:386:16: Warning: reference to free variable Disable showing Disable logging Warning (comp): debian-ispell.el:392:16: Warning: reference to free variable Disable showing Disable logging Warning (comp): debian-ispell.el:393:16: Warning: reference to free variable Disable showing Disable logging Warning (comp): debian-ispell.el:403:24: Warning: assignment to free variable Disable showing Disable logging Warning (comp): debian-ispell.el:403:20: Warning: reference to free variable Disable showing Disable logging [...] Warning (comp): init-general.el:44:7: Warning: assignment to free variable Disable showing Disable logging Warning (comp): init-general.el:45:7: Warning: assignment to free variable Disable showing Disable logging Warning (comp): init-general.el:47:7: Warning: assignment to free variable =E2=80=98Man-width=E2=80=99 Disable showing Disable logging [...] (The file init-general.el is required from my init file.) To reproduce this, I would assume it is sufficient to either run Debian, where the debian-ispell.el file is part of the site-files, or having an init file requiring a file with, for example, the line: (setq display-time-24hr-format t) ; my line 47 above I'm not exactly sure what the best course of action is here. But wouldn't it be better to not show this at all to users, unless they explicitly ask for it? As it stands, it is a bit too noisy and in-your-face, I think. (I also don't understand why the byte-compiler does not complain about these variables.) From unknown Sat Jun 14 03:54:44 2025 X-Loop: help-debbugs@gnu.org Subject: bug#44746: 28.0.50; [feature/native-comp] Noisy "*Warnings*" buffer shown on start Resent-From: Andrea Corallo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 20 Nov 2020 08:32:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 44746 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: To: Stefan Kangas Cc: 44746@debbugs.gnu.org Received: via spool by 44746-submit@debbugs.gnu.org id=B44746.16058610838570 (code B ref 44746); Fri, 20 Nov 2020 08:32:02 +0000 Received: (at 44746) by debbugs.gnu.org; 20 Nov 2020 08:31:23 +0000 Received: from localhost ([127.0.0.1]:41862 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kg1pD-0002EA-3a for submit@debbugs.gnu.org; Fri, 20 Nov 2020 03:31:23 -0500 Received: from mx.sdf.org ([205.166.94.24]:53562) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kg1pB-0002E1-Hw for 44746@debbugs.gnu.org; Fri, 20 Nov 2020 03:31:22 -0500 Received: from mab (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTP id 0AK8VIKS013116; Fri, 20 Nov 2020 08:31:18 GMT From: Andrea Corallo References: Date: Fri, 20 Nov 2020 08:31:18 +0000 In-Reply-To: (Stefan Kangas's message of "Thu, 19 Nov 2020 16:50:08 -0800") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.0 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Stefan Kangas writes: > Every time I start Emacs after recompilation or clearing cache, I see a > "*Warnings*" buffer popup in a new window, filled with a large amount of > warnings like these: > > Warning (comp): debian-ispell.el:229:17: Warning: assignment to free > variable Disable showing Disable logging > Warning (comp): debian-ispell.el:228:28: Warning: reference to free > variable =E2=80=98really-hunspell=E2=80=99 Disable showing Disable logging > Warning (comp): debian-ispell.el:386:16: Warning: reference to free > variable Disable showing Disable logging > Warning (comp): debian-ispell.el:392:16: Warning: reference to free > variable Disable showing Disable logging > Warning (comp): debian-ispell.el:393:16: Warning: reference to free > variable Disable showing Disable logging > Warning (comp): debian-ispell.el:403:24: Warning: assignment to free > variable Disable showing Disable logging > Warning (comp): debian-ispell.el:403:20: Warning: reference to free > variable Disable showing Disable logging > [...] > Warning (comp): init-general.el:44:7: Warning: assignment to free > variable Disable showing Disable logging > Warning (comp): init-general.el:45:7: Warning: assignment to free > variable Disable showing Disable logging > Warning (comp): init-general.el:47:7: Warning: assignment to free > variable =E2=80=98Man-width=E2=80=99 Disable showing Disable logging > [...] > > (The file init-general.el is required from my init file.) > > To reproduce this, I would assume it is sufficient to either run Debian, > where the debian-ispell.el file is part of the site-files, or having an > init file requiring a file with, for example, the line: > > (setq display-time-24hr-format t) ; my line 47 above > > > I'm not exactly sure what the best course of action is here. But > wouldn't it be better to not show this at all to users, unless they > explicitly ask for it? As it stands, it is a bit too noisy and > in-your-face, I think. > > (I also don't understand why the byte-compiler does not complain about > these variables.) The byte compiler does not complain because when it compiles these definitions happen to be present in the compilation environment (read the file defining these variables was by chance already loaded). Each file should be consistent and compilable regardless the load history of the Emacs used to compile (read specify the correct requires). Given async compilation start from a fresh Emacs it's more sensitive into spotting these errors or warnings. Reporting these messages to the user as warnings was the result of #44168. Before #44168 these messages where only reported into the *Async-native-compile-log*. This was requested by a number of people because more than one package missed requiring the feature containing some macro definition. This indeed resulted in miscompilations with the diagnostic message being "hidden" in *Async-native-compile-log*. Compilation units should *not* rely on the compiler environment for their definitions. So yeah these are real warnings or errors and package developers need to get them somehow. They could manifest also on non nativecomp builds if the compilation order or something else chance. So this is not only a nice clean-up but also a real fix IMO. I'm not sure what's the best action we can take to reduce the verbosity but keep developers informed at the same time. Andrea From unknown Sat Jun 14 03:54:44 2025 X-Loop: help-debbugs@gnu.org Subject: bug#44746: 28.0.50; [feature/native-comp] Noisy "*Warnings*" buffer shown on start Resent-From: Andrea Corallo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 25 Feb 2021 23:00:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 44746 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: To: 44746@debbugs.gnu.org Cc: stefan@marxist.se X-Debbugs-Original-To: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" X-Debbugs-Original-Cc: 44746@debbugs.gnu.org, Stefan Kangas Received: via spool by submit@debbugs.gnu.org id=B.161429395812358 (code B ref -1); Thu, 25 Feb 2021 23:00:02 +0000 Received: (at submit) by debbugs.gnu.org; 25 Feb 2021 22:59:18 +0000 Received: from localhost ([127.0.0.1]:39682 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lFPbJ-0003DG-G7 for submit@debbugs.gnu.org; Thu, 25 Feb 2021 17:59:18 -0500 Received: from lists.gnu.org ([209.51.188.17]:55986) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lFPbI-0003D9-9T for submit@debbugs.gnu.org; Thu, 25 Feb 2021 17:59:16 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:59930) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lFPbG-0005MO-W4 for bug-gnu-emacs@gnu.org; Thu, 25 Feb 2021 17:59:16 -0500 Received: from mx.sdf.org ([205.166.94.24]:61614) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lFPb5-0004uL-9x for bug-gnu-emacs@gnu.org; Thu, 25 Feb 2021 17:59:14 -0500 Received: from mab (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 11PMwsox006202 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Thu, 25 Feb 2021 22:58:55 GMT From: Andrea Corallo References: Date: Thu, 25 Feb 2021 22:58:54 +0000 In-Reply-To: (Andrea Corallo via's message of "Fri, 20 Nov 2020 08:31:18 +0000") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=205.166.94.24; envelope-from=akrl@sdf.org; helo=mx.sdf.org X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Score: -1.4 (-) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.4 (--) Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" writes: > Stefan Kangas writes: > >> Every time I start Emacs after recompilation or clearing cache, I see a >> "*Warnings*" buffer popup in a new window, filled with a large amount of >> warnings like these: >> >> Warning (comp): debian-ispell.el:229:17: Warning: assignment to free >> variable Disable showing Disable logging >> Warning (comp): debian-ispell.el:228:28: Warning: reference to free >> variable =E2=80=98really-hunspell=E2=80=99 Disable showing Disable loggi= ng >> Warning (comp): debian-ispell.el:386:16: Warning: reference to free >> variable Disable showing Disable logging >> Warning (comp): debian-ispell.el:392:16: Warning: reference to free >> variable Disable showing Disable logging >> Warning (comp): debian-ispell.el:393:16: Warning: reference to free >> variable Disable showing Disable logging >> Warning (comp): debian-ispell.el:403:24: Warning: assignment to free >> variable Disable showing Disable logging >> Warning (comp): debian-ispell.el:403:20: Warning: reference to free >> variable Disable showing Disable logging >> [...] >> Warning (comp): init-general.el:44:7: Warning: assignment to free >> variable Disable showing Disable logging >> Warning (comp): init-general.el:45:7: Warning: assignment to free >> variable Disable showing Disable logging >> Warning (comp): init-general.el:47:7: Warning: assignment to free >> variable =E2=80=98Man-width=E2=80=99 Disable showing Disable logging >> [...] >> >> (The file init-general.el is required from my init file.) >> >> To reproduce this, I would assume it is sufficient to either run Debian, >> where the debian-ispell.el file is part of the site-files, or having an >> init file requiring a file with, for example, the line: >> >> (setq display-time-24hr-format t) ; my line 47 above >> >> >> I'm not exactly sure what the best course of action is here. But >> wouldn't it be better to not show this at all to users, unless they >> explicitly ask for it? As it stands, it is a bit too noisy and >> in-your-face, I think. >> >> (I also don't understand why the byte-compiler does not complain about >> these variables.) > > The byte compiler does not complain because when it compiles these > definitions happen to be present in the compilation environment (read > the file defining these variables was by chance already loaded). Each > file should be consistent and compilable regardless the load history of > the Emacs used to compile (read specify the correct requires). > > Given async compilation start from a fresh Emacs it's more sensitive > into spotting these errors or warnings. > > Reporting these messages to the user as warnings was the result of > #44168. Before #44168 these messages where only reported into the > *Async-native-compile-log*. > > This was requested by a number of people because more than one package > missed requiring the feature containing some macro definition. This > indeed resulted in miscompilations with the diagnostic message being > "hidden" in *Async-native-compile-log*. > > Compilation units should *not* rely on the compiler environment for > their definitions. > > So yeah these are real warnings or errors and package developers need to > get them somehow. They could manifest also on non nativecomp builds if > the compilation order or something else chance. So this is not only a > nice clean-up but also a real fix IMO. > > I'm not sure what's the best action we can take to reduce the verbosity > but keep developers informed at the same time. > > Andrea To complete this answer, ATM is possible to gate all warnings reported by async native compilations leveraging the `comp-async-report-warnings-errors' customize. Is this sufficient to close this bug or do we like to discuss this default? My opinion (got it from the discussion on emacs-devel) is that at least for now would be good to keep `comp-async-report-warnings-errors' to t for the reason I've explained in the mail I'm quoting. Perhaps we could think about revisiting this default but probably in the future. Thanks Andrea From unknown Sat Jun 14 03:54:44 2025 X-Loop: help-debbugs@gnu.org Subject: bug#44746: 28.0.50; [feature/native-comp] Noisy "*Warnings*" buffer shown on start Resent-From: Stefan Kangas Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 26 Feb 2021 00:00:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 44746 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: To: akrl@sdf.org, 44746@debbugs.gnu.org X-Debbugs-Original-To: Andrea Corallo , "Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors" X-Debbugs-Original-Cc: 44746@debbugs.gnu.org Received: via spool by submit@debbugs.gnu.org id=B.161429757217845 (code B ref -1); Fri, 26 Feb 2021 00:00:02 +0000 Received: (at submit) by debbugs.gnu.org; 25 Feb 2021 23:59:32 +0000 Received: from localhost ([127.0.0.1]:39742 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lFQXb-0004dl-TD for submit@debbugs.gnu.org; Thu, 25 Feb 2021 18:59:32 -0500 Received: from lists.gnu.org ([209.51.188.17]:53824) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lFQXU-0004dI-Tv for submit@debbugs.gnu.org; Thu, 25 Feb 2021 18:59:26 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:50414) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lFQXU-0004eB-7M for bug-gnu-emacs@gnu.org; Thu, 25 Feb 2021 18:59:24 -0500 Received: from mail-pl1-f182.google.com ([209.85.214.182]:39390) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lFQXS-0005Vp-20 for bug-gnu-emacs@gnu.org; Thu, 25 Feb 2021 18:59:23 -0500 Received: by mail-pl1-f182.google.com with SMTP id k22so4133933pll.6 for ; Thu, 25 Feb 2021 15:59:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=FmewCXfVMp7Xc8h1lEDPWN90PZjheUWLn2qLUJmV9nE=; b=hvKGRrjzhtOOFeXDoyHyUo8J0LypvN8gqdtqqzx94tiKn1l4D6s0O7LvfltTOygfYy QNWpKysa5FRz5f/o6ScBHqiINdngsaBwD01pTTnl1MVBcGgSOpF2dPHsMn721pKR5Cjq /orY1c/BG7WcqVwUilopFlynfYA1rDWhkYfRCPkKyWUr1wzZW2jdORRSzNVNPZCFeX3Q 80YKJeiawCMVrLyjA8b8DEU50Cy6y6Xw8y47hGGg9Gru+0ueYSm1Zh5hsPKyqP4St2Yj ug02Ge5uGwY+WTYlbElLJ+FZJF6o2pcG9Ndtun8byUcKwtdis0i7x18ZHdQGUUUxcYKX 7l3A== X-Gm-Message-State: AOAM530CoBl3L7AXNMQyGeGn/DRv++8K1kX76WOL7wtq12t6vWmhpGzW FJaIExoYWb9YN5fCwEoYUdJ3prUjpJh0+2Mlw8E= X-Google-Smtp-Source: ABdhPJxdSWJg1H8qMBPBsi8W01YkREvJVs6eNLF64qsQYk6Iq6Goctd+9X8XSYOP1oBWJwWnBwsX0yF1bboSChHeZOs= X-Received: by 2002:a17:90a:bd84:: with SMTP id z4mr379691pjr.179.1614297559517; Thu, 25 Feb 2021 15:59:19 -0800 (PST) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Thu, 25 Feb 2021 17:59:18 -0600 From: Stefan Kangas In-Reply-To: References: MIME-Version: 1.0 Date: Thu, 25 Feb 2021 17:59:18 -0600 Message-ID: Content-Type: text/plain; charset="UTF-8" Received-SPF: pass client-ip=209.85.214.182; envelope-from=stefankangas@gmail.com; helo=mail-pl1-f182.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-Spam-Score: -0.8 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.8 (-) Andrea Corallo writes: >> The byte compiler does not complain because when it compiles these >> definitions happen to be present in the compilation environment (read >> the file defining these variables was by chance already loaded). Each >> file should be consistent and compilable regardless the load history of >> the Emacs used to compile (read specify the correct requires). >> >> Given async compilation start from a fresh Emacs it's more sensitive >> into spotting these errors or warnings. >> >> Reporting these messages to the user as warnings was the result of >> #44168. Before #44168 these messages where only reported into the >> *Async-native-compile-log*. >> >> This was requested by a number of people because more than one package >> missed requiring the feature containing some macro definition. This >> indeed resulted in miscompilations with the diagnostic message being >> "hidden" in *Async-native-compile-log*. >> >> Compilation units should *not* rely on the compiler environment for >> their definitions. >> >> So yeah these are real warnings or errors and package developers need to >> get them somehow. They could manifest also on non nativecomp builds if >> the compilation order or something else chance. So this is not only a >> nice clean-up but also a real fix IMO. (Sorry I didn't reply properly the last time around.) The above reasoning is correct and valid for any ELisp package, I think. But most of the warnings I see are actually from my init files. There, I specifically do not want to `require' everything I need as that would slow down startup. It also places undue burden on mere users that want to customize this or that option from their init file. And users can and do customize pretty much anything. This is Emacs after all. So we can't really auto load stuff either... Perhaps we need some special casing to detect what is an init file and what is a package? I have no idea how to do that reliably though, so it might be a pipe dream. Or maybe this will all be fixed, for some definition of fixed, when we flip the default? >> I'm not sure what's the best action we can take to reduce the verbosity >> but keep developers informed at the same time. >> >> Andrea > > To complete this answer, ATM is possible to gate all warnings reported > by async native compilations leveraging the > `comp-async-report-warnings-errors' customize. > > Is this sufficient to close this bug or do we like to discuss this > default? > > My opinion (got it from the discussion on emacs-devel) is that at least > for now would be good to keep `comp-async-report-warnings-errors' to t > for the reason I've explained in the mail I'm quoting. Perhaps we could > think about revisiting this default but probably in the future. Yes, I agree with the plan to leave the default for now and think about changing it closer to release. It is your decision to close this bug or not. As far as I'm concerned, I think the necessary clarifications have been made and it is clear that you are on top of things. The other option is to mark it as blocking Emacs 28.1 (Bug#39202) as a reminder. Thanks again for your hard work on this branch! I've been using it daily since August and it is running just fine here. From unknown Sat Jun 14 03:54:44 2025 X-Loop: help-debbugs@gnu.org Subject: bug#44746: 28.0.50; [feature/native-comp] Noisy "*Warnings*" buffer shown on start Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 26 Feb 2021 07:18:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 44746 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: To: Andrea Corallo Cc: 44746@debbugs.gnu.org, stefan@marxist.se Received: via spool by 44746-submit@debbugs.gnu.org id=B44746.16143238809240 (code B ref 44746); Fri, 26 Feb 2021 07:18:02 +0000 Received: (at 44746) by debbugs.gnu.org; 26 Feb 2021 07:18:00 +0000 Received: from localhost ([127.0.0.1]:40163 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lFXNw-0002Oy-Cj for submit@debbugs.gnu.org; Fri, 26 Feb 2021 02:18:00 -0500 Received: from eggs.gnu.org ([209.51.188.92]:42778) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lFXNu-0002Ol-Ns for 44746@debbugs.gnu.org; Fri, 26 Feb 2021 02:17:59 -0500 Received: from fencepost.gnu.org ([2001:470:142:3::e]:43181) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lFXNo-0001hi-08; Fri, 26 Feb 2021 02:17:52 -0500 Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2600 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lFXNn-0003yo-Bq; Fri, 26 Feb 2021 02:17:51 -0500 Date: Fri, 26 Feb 2021 09:17:37 +0200 Message-Id: <83o8g7qovi.fsf@gnu.org> From: Eli Zaretskii In-Reply-To: (bug-gnu-emacs@gnu.org) References: X-Spam-Score: -0.7 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) > Cc: stefan@marxist.se > Date: Thu, 25 Feb 2021 22:58:54 +0000 > From: Andrea Corallo via "Bug reports for GNU Emacs, > the Swiss army knife of text editors" > > To complete this answer, ATM is possible to gate all warnings reported > by async native compilations leveraging the > `comp-async-report-warnings-errors' customize. > > Is this sufficient to close this bug or do we like to discuss this > default? I think we can close this, yes. Basically, you are saying that most of these warnings will go away once we get our act together and fix all the missing 'require's. Btw, I think the doc string of comp-async-report-warnings-errors could use some love: as it stands now, I needed to read the code where it is used to understand what it does, and why it is a defcustom. Some of the explanation you, Andrea, wrote in this thread could find its way into the doc string and make it much more clear. > My opinion (got it from the discussion on emacs-devel) is that at least > for now would be good to keep `comp-async-report-warnings-errors' to t > for the reason I've explained in the mail I'm quoting. Agreed. Thanks. From unknown Sat Jun 14 03:54:44 2025 X-Loop: help-debbugs@gnu.org Subject: bug#44746: 28.0.50; [feature/native-comp] Noisy "*Warnings*" buffer shown on start Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 26 Feb 2021 07:20:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 44746 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: To: Stefan Kangas Cc: 44746@debbugs.gnu.org, akrl@sdf.org Received: via spool by 44746-submit@debbugs.gnu.org id=B44746.16143240019436 (code B ref 44746); Fri, 26 Feb 2021 07:20:01 +0000 Received: (at 44746) by debbugs.gnu.org; 26 Feb 2021 07:20:01 +0000 Received: from localhost ([127.0.0.1]:40169 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lFXPs-0002S2-QZ for submit@debbugs.gnu.org; Fri, 26 Feb 2021 02:20:01 -0500 Received: from eggs.gnu.org ([209.51.188.92]:43236) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lFXPq-0002Ro-L0 for 44746@debbugs.gnu.org; Fri, 26 Feb 2021 02:19:58 -0500 Received: from fencepost.gnu.org ([2001:470:142:3::e]:43206) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lFXPl-0002fd-EV; Fri, 26 Feb 2021 02:19:53 -0500 Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2729 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lFXPi-00046U-7o; Fri, 26 Feb 2021 02:19:53 -0500 Date: Fri, 26 Feb 2021 09:19:39 +0200 Message-Id: <83mtvrqos4.fsf@gnu.org> From: Eli Zaretskii In-Reply-To: (message from Stefan Kangas on Thu, 25 Feb 2021 17:59:18 -0600) References: X-Spam-Score: -0.7 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) > From: Stefan Kangas > Date: Thu, 25 Feb 2021 17:59:18 -0600 > > The above reasoning is correct and valid for any ELisp package, I think. > > But most of the warnings I see are actually from my init files. There, > I specifically do not want to `require' everything I need as that would > slow down startup. It also places undue burden on mere users that want > to customize this or that option from their init file. But you could bind that variable to nil when loading those init files, right? From unknown Sat Jun 14 03:54:44 2025 MIME-Version: 1.0 X-Mailer: MIME-tools 5.505 (Entity 5.505) X-Loop: help-debbugs@gnu.org From: help-debbugs@gnu.org (GNU bug Tracking System) To: Stefan Kangas Subject: bug#44746: closed (Re: bug#44746: 28.0.50; [feature/native-comp] Noisy "*Warnings*" buffer shown on start) Message-ID: References: X-Gnu-PR-Message: they-closed 44746 X-Gnu-PR-Package: emacs Reply-To: 44746@debbugs.gnu.org Date: Fri, 26 Feb 2021 14:28:03 +0000 Content-Type: multipart/mixed; boundary="----------=_1614349683-24115-1" This is a multi-part message in MIME format... ------------=_1614349683-24115-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Your bug report #44746: 28.0.50; [feature/native-comp] Noisy "*Warnings*" buffer shown on s= tart which was filed against the emacs package, has been closed. The explanation is attached below, along with your original report. If you require more details, please reply to 44746@debbugs.gnu.org. --=20 44746: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D44746 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems ------------=_1614349683-24115-1 Content-Type: message/rfc822 Content-Disposition: inline Content-Transfer-Encoding: 7bit Received: (at 44746-done) by debbugs.gnu.org; 26 Feb 2021 14:27:31 +0000 Received: from localhost ([127.0.0.1]:40504 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lFe5a-0006Fq-Tg for submit@debbugs.gnu.org; Fri, 26 Feb 2021 09:27:31 -0500 Received: from mx.sdf.org ([205.166.94.24]:56922) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lFe5X-0006Fg-CZ for 44746-done@debbugs.gnu.org; Fri, 26 Feb 2021 09:27:29 -0500 Received: from mab (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 11QERQoR015429 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Fri, 26 Feb 2021 14:27:26 GMT From: Andrea Corallo To: Eli Zaretskii Subject: Re: bug#44746: 28.0.50; [feature/native-comp] Noisy "*Warnings*" buffer shown on start References: <83o8g7qovi.fsf@gnu.org> Date: Fri, 26 Feb 2021 14:27:26 +0000 In-Reply-To: <83o8g7qovi.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 26 Feb 2021 09:17:37 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 44746-done Cc: 44746-done@debbugs.gnu.org, stefan@marxist.se X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Eli Zaretskii writes: >> Cc: stefan@marxist.se >> Date: Thu, 25 Feb 2021 22:58:54 +0000 >> From: Andrea Corallo via "Bug reports for GNU Emacs, >> the Swiss army knife of text editors" >> >> To complete this answer, ATM is possible to gate all warnings reported >> by async native compilations leveraging the >> `comp-async-report-warnings-errors' customize. >> >> Is this sufficient to close this bug or do we like to discuss this >> default? > > I think we can close this, yes. Basically, you are saying that most > of these warnings will go away once we get our act together and fix > all the missing 'require's. Exactly, consider that (I think) most of these warnings are coming from packages non in emacs.git. Code in emacs.git being regularly compiled during the build process in a fresh enviroment is typically cleaner from this prespective IME. > Btw, I think the doc string of comp-async-report-warnings-errors could > use some love: as it stands now, I needed to read the code where it is > used to understand what it does, and why it is a defcustom. Some of > the explanation you, Andrea, wrote in this thread could find its way > into the doc string and make it much more clear. Right I tried with ad74b1b2b6, please have a look an let me know in case. >> My opinion (got it from the discussion on emacs-devel) is that at least >> for now would be good to keep `comp-async-report-warnings-errors' to t >> for the reason I've explained in the mail I'm quoting. > > Agreed. > > Thanks. Closing this then. Thanks Andrea ------------=_1614349683-24115-1 Content-Type: message/rfc822 Content-Disposition: inline Content-Transfer-Encoding: 7bit Received: (at submit) by debbugs.gnu.org; 20 Nov 2020 00:50:15 +0000 Received: from localhost ([127.0.0.1]:41391 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kfucx-0005WR-5R for submit@debbugs.gnu.org; Thu, 19 Nov 2020 19:50:15 -0500 Received: from lists.gnu.org ([209.51.188.17]:44700) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kfucv-0005WJ-0R for submit@debbugs.gnu.org; Thu, 19 Nov 2020 19:50:13 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:34090) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kfucu-0003XI-NQ for bug-gnu-emacs@gnu.org; Thu, 19 Nov 2020 19:50:12 -0500 Received: from mail-ed1-f52.google.com ([209.85.208.52]:34443) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kfucs-0004ed-Sw for bug-gnu-emacs@gnu.org; Thu, 19 Nov 2020 19:50:12 -0500 Received: by mail-ed1-f52.google.com with SMTP id a15so7821179edy.1 for ; Thu, 19 Nov 2020 16:50:10 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:date:message-id:subject:to :content-transfer-encoding; bh=jKTDG9xYM9ifU/u7KFhyjOcso5TaFvGnj20pCxo1LNQ=; b=Aa8J68q+hLoVYhhsirWGtS71rFfuMUsbBjM6N16tsOUz5ovZLyEynCg/ERw/HEmmGC JzoFV3kLeb36jKwDfSEoubIUV6RJzZb1fU2UxXQjzDXuV9w4GE1R84aVldx7k5HAZUhm eDGfjmVvNKTYKedEJnQQpELPQuf6uGH2L1b+UBDDTk57xnM2zQE5cE17keMy4jfuzuZV XWyEa3qzaJPzuEa+NSgaVoFNEhnGi0i97lKpUOhj+J5C+dZmXAu6qMPCjG5jHoSVI1Tm Mlu54U5oBQVIDtLnCRiC8ltPKLD3aeyo7xmZdzf1Cq8psAPSNpcElRA65HmkXqU/5h2m 0xvA== X-Gm-Message-State: AOAM5316Mjy7OzOnPlljETfkwo1ovxLgNOpFoi18ymxqpxHvpG9xkOru a48dQOiXFIkcuwGsOLAMzyZhkXJzq36V7sH/I+I5F9KqwTE= X-Google-Smtp-Source: ABdhPJw4GQKUjdKbuQEv/rc/+lunqVjjaLIHtko3m0Q6DWPgSKLtSSYsohbVr3KOxn/NzySOP5kM3A52i3NnVqCmFTA= X-Received: by 2002:a50:9f61:: with SMTP id b88mr34656027edf.282.1605833409016; Thu, 19 Nov 2020 16:50:09 -0800 (PST) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Thu, 19 Nov 2020 16:50:08 -0800 From: Stefan Kangas MIME-Version: 1.0 Date: Thu, 19 Nov 2020 16:50:08 -0800 Message-ID: Subject: 28.0.50; [feature/native-comp] Noisy "*Warnings*" buffer shown on start To: bug-gnu-emacs@gnu.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=209.85.208.52; envelope-from=stefankangas@gmail.com; helo=mail-ed1-f52.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-Spam-Score: 0.7 (/) X-Debbugs-Envelope-To: submit X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.8 (-) Every time I start Emacs after recompilation or clearing cache, I see a "*Warnings*" buffer popup in a new window, filled with a large amount of warnings like these: Warning (comp): debian-ispell.el:229:17: Warning: assignment to free variable Disable showing Disable logging Warning (comp): debian-ispell.el:228:28: Warning: reference to free variable =E2=80=98really-hunspell=E2=80=99 Disable showing Disable logging Warning (comp): debian-ispell.el:386:16: Warning: reference to free variable Disable showing Disable logging Warning (comp): debian-ispell.el:392:16: Warning: reference to free variable Disable showing Disable logging Warning (comp): debian-ispell.el:393:16: Warning: reference to free variable Disable showing Disable logging Warning (comp): debian-ispell.el:403:24: Warning: assignment to free variable Disable showing Disable logging Warning (comp): debian-ispell.el:403:20: Warning: reference to free variable Disable showing Disable logging [...] Warning (comp): init-general.el:44:7: Warning: assignment to free variable Disable showing Disable logging Warning (comp): init-general.el:45:7: Warning: assignment to free variable Disable showing Disable logging Warning (comp): init-general.el:47:7: Warning: assignment to free variable =E2=80=98Man-width=E2=80=99 Disable showing Disable logging [...] (The file init-general.el is required from my init file.) To reproduce this, I would assume it is sufficient to either run Debian, where the debian-ispell.el file is part of the site-files, or having an init file requiring a file with, for example, the line: (setq display-time-24hr-format t) ; my line 47 above I'm not exactly sure what the best course of action is here. But wouldn't it be better to not show this at all to users, unless they explicitly ask for it? As it stands, it is a bit too noisy and in-your-face, I think. (I also don't understand why the byte-compiler does not complain about these variables.) ------------=_1614349683-24115-1-- From unknown Sat Jun 14 03:54:44 2025 X-Loop: help-debbugs@gnu.org Subject: bug#44746: 28.0.50; [feature/native-comp] Noisy "*Warnings*" buffer shown on start Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 26 Feb 2021 14:53:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 44746 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: To: Andrea Corallo Cc: 44746@debbugs.gnu.org, stefan@marxist.se Received: via spool by 44746-submit@debbugs.gnu.org id=B44746.161435117326398 (code B ref 44746); Fri, 26 Feb 2021 14:53:02 +0000 Received: (at 44746) by debbugs.gnu.org; 26 Feb 2021 14:52:53 +0000 Received: from localhost ([127.0.0.1]:40538 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lFeU9-0006ri-3e for submit@debbugs.gnu.org; Fri, 26 Feb 2021 09:52:53 -0500 Received: from eggs.gnu.org ([209.51.188.92]:59786) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lFeU7-0006rW-VH for 44746@debbugs.gnu.org; Fri, 26 Feb 2021 09:52:52 -0500 Received: from fencepost.gnu.org ([2001:470:142:3::e]:33935) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lFeU1-0006HX-Ki; Fri, 26 Feb 2021 09:52:45 -0500 Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:3247 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lFeTy-0004YH-8j; Fri, 26 Feb 2021 09:52:43 -0500 Date: Fri, 26 Feb 2021 16:52:30 +0200 Message-Id: <83y2faq3td.fsf@gnu.org> From: Eli Zaretskii In-Reply-To: (message from Andrea Corallo on Fri, 26 Feb 2021 14:27:26 +0000) References: <83o8g7qovi.fsf@gnu.org> X-Spam-Score: -0.7 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) > From: Andrea Corallo > Cc: 44746-done@debbugs.gnu.org, stefan@marxist.se > Date: Fri, 26 Feb 2021 14:27:26 +0000 > > > Btw, I think the doc string of comp-async-report-warnings-errors could > > use some love: as it stands now, I needed to read the code where it is > > used to understand what it does, and why it is a defcustom. Some of > > the explanation you, Andrea, wrote in this thread could find its way > > into the doc string and make it much more clear. > > Right I tried with ad74b1b2b6, please have a look an let me know in > case. Thanks, it was very good. I made some minor improvements (the main of which is to tell that people who are annoyed by the warnings should set this to a nil value). From unknown Sat Jun 14 03:54:44 2025 X-Loop: help-debbugs@gnu.org Subject: bug#44746: 28.0.50; [feature/native-comp] Noisy "*Warnings*" buffer shown on start Resent-From: Stefan Kangas Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 26 Feb 2021 17:27:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 44746 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: To: Eli Zaretskii Cc: 44746@debbugs.gnu.org, akrl@sdf.org Received: via spool by 44746-submit@debbugs.gnu.org id=B44746.161436037917997 (code B ref 44746); Fri, 26 Feb 2021 17:27:02 +0000 Received: (at 44746) by debbugs.gnu.org; 26 Feb 2021 17:26:19 +0000 Received: from localhost ([127.0.0.1]:42291 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lFgsc-0004gD-R9 for submit@debbugs.gnu.org; Fri, 26 Feb 2021 12:26:19 -0500 Received: from mail-pj1-f46.google.com ([209.85.216.46]:51973) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lFgsb-0004g1-3k for 44746@debbugs.gnu.org; Fri, 26 Feb 2021 12:26:17 -0500 Received: by mail-pj1-f46.google.com with SMTP id jx13so2909550pjb.1 for <44746@debbugs.gnu.org>; Fri, 26 Feb 2021 09:26:17 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=uWvRQ62XREECUtaAX5p770usIiIQZdei90inTiUiR/o=; b=RgBRWRgo8DGnG+oCJ2MG+EmxQFq0UFQiYc685NL6FlLn5GZKV9ph3pa1H8kNLptyi0 +878BJI4blwhKUGDomGh9TAmYgSkcKO68eO1Djutz4X03l9EYoLiqWloeGvLZIXcFNQ8 J0HkBvUWaIRwdAFZkanZMGkENo2j025scodq4w+16LUvL8UoJ6Xx55g+XG6neGLH1P28 0Yuk7D/gtM6iTFKy/vkwuosneljpoOZmbkemdzuuuRAXd8gq2Oabc4Ks2x/4PjEUR2+P RXLffCwzUlNu0LB/0Tpco+whHbj+KK4xsehXVNKjwfBG3HoZ2PNqezdD9P1SNURT2zWf TbUQ== X-Gm-Message-State: AOAM532QM+URUxbluY8EiYjlhPEpsMt8+DVMMj9Svv/3IuTLw2UgevsD TzyEXh4YNQnyU62rop6AexEN/n/Ib08XTr10Wms= X-Google-Smtp-Source: ABdhPJxfczJ+rkdk+S/+M0F//R9mAmzNH/QizbPInhEWzL7rtvU6GGxMPqYBKyfzxd/iIFfPA4aa21YMozpzRfBED64= X-Received: by 2002:a17:90b:e83:: with SMTP id fv3mr2345005pjb.179.1614360371177; Fri, 26 Feb 2021 09:26:11 -0800 (PST) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Fri, 26 Feb 2021 11:26:10 -0600 From: Stefan Kangas In-Reply-To: <83mtvrqos4.fsf@gnu.org> References: <83mtvrqos4.fsf@gnu.org> MIME-Version: 1.0 Date: Fri, 26 Feb 2021 11:26:10 -0600 Message-ID: Content-Type: text/plain; charset="UTF-8" X-Spam-Score: 0.5 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -0.5 (/) Eli Zaretskii writes: > But you could bind that variable to nil when loading those init files, > right? I would assume it would work, but I haven't tried it. But that should solve the issue locally, yes. From unknown Sat Jun 14 03:54:44 2025 X-Loop: help-debbugs@gnu.org Subject: bug#44746: 28.0.50; [feature/native-comp] Noisy "*Warnings*" buffer shown on start Resent-From: Andrea Corallo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 26 Feb 2021 18:57:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 44746 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: To: Eli Zaretskii Cc: 44746@debbugs.gnu.org, stefan@marxist.se Received: via spool by 44746-submit@debbugs.gnu.org id=B44746.161436579911298 (code B ref 44746); Fri, 26 Feb 2021 18:57:02 +0000 Received: (at 44746) by debbugs.gnu.org; 26 Feb 2021 18:56:39 +0000 Received: from localhost ([127.0.0.1]:42533 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lFiI3-0002w8-Aj for submit@debbugs.gnu.org; Fri, 26 Feb 2021 13:56:39 -0500 Received: from mx.sdf.org ([205.166.94.24]:52666) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lFiI1-0002w1-KK for 44746@debbugs.gnu.org; Fri, 26 Feb 2021 13:56:38 -0500 Received: from mab (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 11QIuaGF025609 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Fri, 26 Feb 2021 18:56:36 GMT From: Andrea Corallo References: <83o8g7qovi.fsf@gnu.org> <83y2faq3td.fsf@gnu.org> Date: Fri, 26 Feb 2021 18:56:36 +0000 In-Reply-To: <83y2faq3td.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 26 Feb 2021 16:52:30 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.0 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Eli Zaretskii writes: >> From: Andrea Corallo >> Cc: 44746-done@debbugs.gnu.org, stefan@marxist.se >> Date: Fri, 26 Feb 2021 14:27:26 +0000 >> >> > Btw, I think the doc string of comp-async-report-warnings-errors could >> > use some love: as it stands now, I needed to read the code where it is >> > used to understand what it does, and why it is a defcustom. Some of >> > the explanation you, Andrea, wrote in this thread could find its way >> > into the doc string and make it much more clear. >> >> Right I tried with ad74b1b2b6, please have a look an let me know in >> case. > > Thanks, it was very good. I made some minor improvements (the main of > which is to tell that people who are annoyed by the warnings should > set this to a nil value). Thanks Andrea